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/clownware/product-devWrote 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/clownware/product-dev/spec)<a href="https://agentmods.dev/commands/clownware/product-dev/spec"><img src="https://agentmods.dev/badge/commands/clownware/product-dev/spec/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/clownware/product-dev/spec"><img src="https://agentmods.dev/badge/commands/clownware/product-dev/spec.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.00008 | $0.00302 |
| Opus 5.5 | $0.00003 | $0.00121 |
| Sonnet 5.5 | $0.00002 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
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 1mo 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
Start a technical specification session using the tech-spec skill.
Gate Check
-
Read
.product-dev/context.json. Verify these artifacts exist:solution_concept(required)user_flow(required)
-
If either is missing, report what's needed:
"Technical specs require design artifacts that don't exist yet. Missing: [list]. Run
/product-dev:ideato build a solution concept, then use the product-flow skill to map the user flow."Do not hard-block — if the user insists, proceed with available artifacts and note assumptions.
-
Also check for optional artifacts that improve spec quality:
screen_inventory,prototype_scope,hypothesis_statement.
Execution
-
Spawn the Tech Spec Writer subagent (
plugin/agents/tech-spec-writer.md). -
If
$ARGUMENTSspecifies a focus area, direct the subagent to that section only. Otherwise, run the full sequence: data models → API endpoints → business rules → NFRs. -
The subagent writes intermediate artifacts (
data_models,api_contracts,business_rules,nfr) and a finaltechnical_specto the registry.
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.
- 1mo ago First seen · 32 lines · 8 tokens per session scan A d7f4c5f88f9f
spec is a command published in the GitHub repository clownware/product-dev (3 stars, last pushed 6d ago), licensed Apache-2.0. It adds 8 tokens to every session and 302 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
genshijin-compress
A command for safely shortening Markdown or text files into the genshijin style.
feat
Quick feature commit. Use for new feature, add feature, implement, create new.
nyann:diff-profile
Compare two nyann profiles side-by-side and show what changes between them: hooks, branching, CI, documentation, extras, governance. Useful before switching profiles to understand the impact.
tasks
Inspect Modellix task status and recover tasks after a timeout or unknown submission.
ledger-commit
(Ledger) Review and commit the ledger repo's changes (push only on confirmation).