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.
npx agentmods add commands/zachjxyz/jvn/specgit clone --depth 1 https://github.com/zachjxyz/jvnWrote 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/zachjxyz/jvn/spec)<a href="https://agentmods.dev/commands/zachjxyz/jvn/spec"><img src="https://agentmods.dev/badge/commands/zachjxyz/jvn/spec.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.00006 | $0.00595 |
| Opus 5 | $0.00003 | $0.00298 |
| Sonnet 5 | $0.00001 | $0.00119 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
spec 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 5d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/spec — Create a Feature Specification
You are orchestrating the specification phase. Follow these steps exactly.
User Input
$ARGUMENTS
Step 1: Create Feature via Spec-Kit
Use the Skill tool to invoke the speckit-specify skill:
Skill(skill: "speckit-specify", args: "$ARGUMENTS")
This creates:
- A feature branch (NNN-short-name)
- A
specs/NNN-short-name/directory - A base
spec.mdfrom spec-kit's template
Wait for completion. Note the spec path from the output.
Step 2: Enrich with Product Manager
Use the Task tool to invoke the product-manager agent:
Task(subagent_type: "product-manager",
description: "Enrich feature specification",
prompt: "Read the specification at specs/{feature}/spec.md. Enhance it with:
- Deeper user stories with acceptance criteria
- Non-functional requirements (performance, security, scalability)
- Clear scope boundaries (in scope / out of scope)
- Success criteria (measurable, technology-agnostic)
- Risks and open questions
If .specify/memory/constitution.md exists, validate feature alignment.
Write the enriched content back to the same file.")
Step 3: Add Data Considerations
Use the Task tool to invoke the data-analyst agent:
Task(subagent_type: "data-analyst",
description: "Add data brief to specification",
prompt: "Read the specification at specs/{feature}/spec.md. Append a Data Brief section covering:
- Data sources and formats
- Pipeline design (ETL/processing steps)
- Model I/O schemas (input features, output format, confidence)
- Validation strategy (data quality checks, schema validation)
- Error handling and fallback behavior
- Performance considerations (batch vs streaming, caching)
Append the Data Brief section to the same file.")
Step 4: Present Summary
Present the enriched specification to the user:
- Show the spec path
- Highlight key user stories and requirements
- Note any
[NEEDS CLARIFICATION]markers
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.
- 5d ago First seen · 82 lines · 6 tokens per session scan A e8561ef5dad4
spec is a command published in the GitHub repository zachjxyz/jvn (2 stars, last pushed 5mo ago), licensed MIT. It adds 6 tokens to every session and 595 once invoked, about $0.0000 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
fix-issue
Command "fix-issue" from KhaiTrang1995/claude-code-structure, covering /project:fix-issue – fix issue command, usage, description, shell steps and run tests after fix.
review
Command "review" from KhaiTrang1995/claude-code-structure, covering /project:review – code review command, usage, description, output format and shell step.
audit
Audit a project's Claude Code adoption and show the score with recommendations.
fix
Fix this project's missing Claude Code setup by writing real CLAUDE.md content, skills, and subagents.
generate-agents
Generate a few subagents matched to this project's detected language(s).
checklist
Generate a custom checklist for the current feature based on user requirements.