Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/ngerakines/jdWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/ngerakines/jd/jdex-audit)<a href="https://agentmods.dev/commands/ngerakines/jd/jdex-audit"><img src="https://agentmods.dev/badge/commands/ngerakines/jd/jdex-audit.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00014 | $0.00357 |
| Opus 5 | $0.00007 | $0.00179 |
| Sonnet 5 | $0.00003 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
jdex-audit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Audit JDex
Compare a system's JDex against its actual folder structure, flagging orphaned entries, undocumented folders, name mismatches, and +SUB index issues.
Arguments
$ARGUMENTS may contain a system code (e.g., P10) to audit a specific
system. If no argument is provided, list all available systems and ask which
to audit.
Workflow
- Load the target system's JDex.
- Snapshot the filesystem to depth 3.
- Compare JDex entries against folders:
- Orphaned JDex entries (in JDex, no folder)
- Undocumented folders (folder exists, not in JDex)
- Name mismatches between JDex and folder names
- Check +SUB index files against +SUB folders.
- Report findings in a structured table.
- Offer fixes: Add missing JDex entries, update +SUB indexes, or flag items that need user decisions.
Safe Fixes
- Adding undocumented folders to the JDex
- Updating +SUB index files with missing entries
Requires User Decision
- Orphaned JDex entries (create folder or remove entry?)
- Name mismatches (which name is correct?)
- Deleting or renaming any folder
Examples
/jd:jdex-audit
/jd:jdex-audit P10
/jd:jdex-audit F50
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 50 lines · 14 tokens per session scan A 0d8cc0d1c051
jdex-audit is a command published in the GitHub repository ngerakines/jd (7 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 357 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.