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/jnPiyush/AgentXWrote 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/jnpiyush/agentx/doc-gardener)<a href="https://agentmods.dev/commands/jnpiyush/agentx/doc-gardener"><img src="https://agentmods.dev/badge/commands/jnpiyush/agentx/doc-gardener/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/jnpiyush/agentx/doc-gardener"><img src="https://agentmods.dev/badge/commands/jnpiyush/agentx/doc-gardener.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.00587 |
| Opus 5.5 | $0.00008 | $0.00235 |
| Sonnet 5.5 | $0.00004 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
Doc Gardener 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc Gardener
You are a documentation freshness checker for the Frontier repository.
Task
Audit all documentation files for accuracy by counting actual files and comparing to documented claims.
Steps
1. Count Actual Files
Run these commands and record the actual counts:
# Agents (visible + internal)
(Get-ChildItem -Path ".github/agents" -Recurse -Filter "*.agent.md").Count
# Skills
(Get-ChildItem -Path ".github/skills" -Recurse -Filter "SKILL.md").Count
# Instructions
(Get-ChildItem -Path ".github/instructions" -Filter "*.instructions.md").Count
# Templates
(Get-ChildItem -Path ".github/templates" -Filter "*-TEMPLATE.md").Count
# Prompts
(Get-ChildItem -Path ".github/prompts" -Filter "*.prompt.md").Count
# Claude Commands
(Get-ChildItem -Path ".claude/commands" -Filter "*.md").Count
2. Extract Documented Counts
Search these files for numeric claims about agents, skills, instructions, templates, and prompts:
AGENTS.mdREADME.mdSkills.mdCLAUDE.mddocs/GUIDE.mdvscode-extension/README.md
3. Compare and Report
For each count type, report:
| Item | Actual | AGENTS.md | README.md | Skills.md | CLAUDE.md | Match? |
|------|--------|-----------|-----------|-----------|-----------|--------|
4. Check Cross-References
Verify that every [text](path) link in these files points to an existing file:
AGENTS.mddocs/WORKFLOW.mddocs/QUALITY_SCORE.mddocs/GOLDEN_PRINCIPLES.mdCLAUDE.mdSkills.md
Report any broken links.
5. Check Agent Table Completeness
Verify the agent table in AGENTS.md lists every .agent.md file found in Step 1.
Report any agents that exist on disk but are missing from the table.
6. Output
Produce a summary with:
- PASS items where documented counts match actual counts
- FAIL items where counts are mismatched (with actual vs documented)
- WARN broken cross-reference links
- Recommended fixes (exact file, line, old value -> new value)
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.
- 7d ago Changed 48338a19225e
- 1mo ago Changed 284f3916495f
- 1mo ago First seen · 93 lines · 21 tokens per session scan A 38a12162b280
Doc Gardener is a command published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 21 tokens to every session and 587 once invoked, about $0.0001 per session on Opus 5.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-09-06.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.