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/jnarowski/agentcmdWrote 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/jnarowski/agentcmd/generate-spec)<a href="https://agentmods.dev/commands/jnarowski/agentcmd/generate-spec"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/generate-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/jnarowski/agentcmd/generate-spec"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/generate-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.00014 | $0.03278 |
| Opus 5.5 | $0.00006 | $0.01311 |
| Sonnet 5.5 | $0.00003 | $0.00656 |
| Haiku 4.5 | $0.00001 | $0.00328 |
Grade C, and why
generate-spec scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- prettier-ignore --> How it starts
The opening of the file, as written. The whole thing — 425 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Implementation Spec with Complexity
Generate a well-structured implementation spec with complexity estimates and save it to .agent/specs/todo/[id]-[feature]/spec.md with timestamp-based ID.
Variables
- $context: $1 (optional) - Additional context for autonomous spec generation (e.g., "Add OAuth support with Google and GitHub providers")
Instructions
- IMPORTANT: Use your reasoning model - THINK HARD about feature requirements, design, implementation approach, AND complexity
- Normalize feature name to kebab-case for the folder name
- Replace ALL
<placeholders>with specific details relevant to that section - Create detailed step-by-step tasks grouped logically (e.g., by phase, component, or feature area)
- Assign complexity score (1-10) to EVERY task based on context needs (see Complexity Scale below)
- Order tasks by dependencies (foundation → core → integration)
- Include specific file paths, not generic names
- Make all commands copy-pasteable with expected outputs
- Include comprehensive verification covering build, tests, linting, and manual checks
- Add E2E test tasks if feature has UI
- Keep acceptance criteria measurable
- DO NOT include hour-based estimates anywhere - use complexity points only
Complexity Scale (Context-Focused)
Assign complexity based on context window usage and cognitive load, not time:
- 1-2/10: Trivial - Single file, <50 lines changed, minimal context (config, doc, simple type)
- 3-4/10: Simple - Few files, straightforward logic, low context (single endpoint, basic component)
- 5-6/10: Moderate - Multiple related files, moderate context (DB field + migration + API update)
- 7-8/10: Complex - Cross-cutting change, high context, multiple domains (full-stack feature, state refactor)
- 9-10/10: Very complex - Architectural change, deep codebase knowledge required (major refactor, complex integration)
Key principle: Higher complexity = more context the agent needs to load and understand
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 · 425 lines · 14 tokens per session scan C c4f7eb6d2fff
generate-spec is a command published in the GitHub repository jnarowski/agentcmd (18 stars, last pushed 10mo ago), licensed MIT. It adds 14 tokens to every session and 3,278 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
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).
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
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.