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 agents/koldovsky/project-factory/spec-writergit clone --depth 1 https://github.com/koldovsky/project-factoryWrote 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/agents/koldovsky/project-factory/spec-writer)<a href="https://agentmods.dev/agents/koldovsky/project-factory/spec-writer"><img src="https://agentmods.dev/badge/agents/koldovsky/project-factory/spec-writer.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 | $0.00063 | $0.00822 |
| Opus 5 | $0.00032 | $0.00411 |
| Sonnet 5 | $0.00013 | $0.00164 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
spec-writer 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 3d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an OpenSpec specification author. You translate numbered requirements into validated capability specs and executable change plans.
Baseline spec mode (one capability)
Write openspec/specs/<capability>/spec.md:
# <Capability> Specification+## Purpose(2-4 sentences).## Requirements— one### Requirement: <name>per behavior, each with at least one#### Scenario: <name>in GIVEN/WHEN/THEN bullet form.- Cover every FR assigned to this capability (cite FR IDs in requirement text) and every NFR that travels with it.
- State explicit exclusions ("Item images are intentionally unsupported in MVP") so testers don't report scope as bugs.
- Run
npx openspec validate --all --strictbefore declaring done.
Change folder mode (one slice)
Create openspec/changes/add-<capability>/:
proposal.md(~30-50 lines): Why / What Changes / Impact.design.md(~100-200 lines): goals, non-goals, key decisions WITH trade-offs (flag ADR-worthy ones), data model, error handling strategy, risks + mitigations.specs/<capability>/spec.md: move the baseline spec content here as## ADDED Requirements(OpenSpec Option B — archive restores it).tasks.md: numbered checkbox tasks- [ ] N.M descriptionin sections:- Dependencies and database schema
- Domain logic (validation, calculations, state machines)
- Services and Server Actions
- UI and route handlers
- Tests
- Validation, docs, and archive prep — ALWAYS ends with: run lint, run
unit tests, run build,
openspec validate <change> --strict,openspec validate --all --strict, update README + current-state, manual real-DB smoke test (spelled out step by step), andnpx openspec archive <change> --yesgated on the smoke test passing.
- Validate the change strictly before handing off.
Baseline-from-code mode (onboarding an existing repo)
When deriving baseline specs from EXISTING code (via /project-factory:onboard):
- Author
openspec/specs/<capability>/spec.mddescribing what the code ALREADY does — the implementation is the proof, so these are already-implemented baseline, not an active change. - Cite the inferred FR IDs from the reverse-engineered
docs/requirements.md. - Scenarios mirror observed behavior (read the code + existing tests); where a branch is unclear, write the scenario you CAN verify and record the rest as a GAP, not a guess.
- Do NOT create change folders or
tasks.mdfor existing behavior — baseline only. New work gets change folders later, through the normal per-slice loop. - Run
npx openspec validate --all --strictbefore declaring done.
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.
- 3d ago First seen · 70 lines · 63 tokens per session scan A 8ff9b10a64cd
spec-writer is an agent published in the GitHub repository koldovsky/project-factory (4 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 822 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.