Dippy verify-counts

Verify numerical claims in documentation are still accurate

install
source · Clone the upstream repo
git clone https://github.com/ldayton/Dippy
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ldayton/Dippy "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/skills/verify-counts" ~/.claude/skills/ldayton-dippy-verify-counts && rm -rf "$T"
manifest: .claude/skills/verify-counts/SKILL.md
source content

Verify all count assertions in documentation against actual values.

Claims to Verify

LocationClaimVerification
README.md:14
14,000+ testsDippy + Parable combined
../Dippy.wiki/Reference/Security-Model.md:79
Over 200 read-only commandsSIMPLE_SAFE count
../Dippy.wiki/Reference/Security-Model.md:94
Over 80 toolsCLI handler count
../Dippy.wiki/Reference/Handler-Model.md:210
80+ handlersCLI handler count

Verification Commands

Dippy tests:

uv run pytest --collect-only -q 2>/dev/null | tail -1

Parable tests: Check table in

/Users/lily/source/Parable/tests/README.md

SIMPLE_SAFE count:

uv run python -c "from src.dippy.core.allowlists import SIMPLE_SAFE; print(len(SIMPLE_SAFE))"

CLI handlers:

ls -1 src/dippy/cli/*.py | grep -v __init__ | wc -l

Output

Report each claim with:

  • Documented value
  • Actual value
  • Status (PASS/FAIL/STALE)

Status Criteria

  • PASS: Actual value is within ~10% of documented value
  • STALE: Claim is technically true but significantly outdated (e.g., "50+" when actual is 77)
  • FAIL: Claim is false

If any claim is STALE or FAIL, note which file(s) need updating.