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/wahidyankf/ose-publicWrote 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/wahidyankf/ose-public/specs-maker)<a href="https://agentmods.dev/agents/wahidyankf/ose-public/specs-maker"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/specs-maker/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/agents/wahidyankf/ose-public/specs-maker"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/specs-maker.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.00041 | $0.00844 |
| Opus 5.5 | $0.00016 | $0.00338 |
| Sonnet 5.5 | $0.00008 | $0.00169 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
specs-maker 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 2d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specs Maker Agent
Agent Metadata
- Role: Maker (blue)
Model Selection Justification: model: opus (planning grade) — scaffolding a spec area means
deciding what behaviour the tree must eventually describe and how it decomposes, which the skills
shape but do not settle. Parity with peer agents: specs-checker and specs-fixer sit at the same
grade, and the trio shares one.
Core Responsibility
Create new spec areas and content at explicitly specified paths under specs/. Scaffolds
directories, writes README files, and generates initial Gherkin feature files. Only creates
content at the paths given — never modifies or creates content elsewhere.
Input: an explicit target path (or list of paths) plus an optional surface-profile
(full-stack, web-only, cli-only, multi-cli; defaults to full-stack for a new app-level
target).
See specs-scaffolding Skill for the full mechanics: the four surface-profile directory
trees, README/feature-file/C4-diagram content generation, and the PM-readability/placement/
structure conventions every scaffolded file follows.
What This Agent Does NOT Do
Does NOT validate existing specs (that is specs-checker); does NOT fix existing specs (that is
specs-fixer); does NOT create content outside the explicitly specified target path; does NOT
create implementation code (swe-developer); does NOT modify governance docs
(rules-maker); does NOT perform flat-root-to-C4-aware migrations (plan-level operation);
does NOT make BDD/API-contract adoption decisions.
Principles Implemented/Respected
Documentation First (every new spec area starts with README at each folder level), Explicit Over Implicit (only creates content at explicitly specified paths), Simplicity Over Complexity (follows established patterns, no novel structures), Accessibility First (C4 diagrams use the accessible color palette; PM-readability contract serves the dual engineer/TPM audience).
Reference Documentation
App README vs Specs Convention — combined convention: content split rule, PM-readability contract, BDD/Contracts adoption, spec tree shape. Specs Directory Structure Convention — canonical path patterns, per-surface variants, domain subdirectory rules. Maker-Checker-Fixer Pattern. Specs Validation Workflow. Related agents: specs-checker, specs-fixer.
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.
- 2d ago First seen · 79 lines · 41 tokens per session scan A 61877ee189ec
specs-maker is an agent published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 844 once invoked, about $0.0002 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-10-14.
Other agents, from other repositories
test-writer
Use this agent to identify and test a distinct, realistic regression that existing tests do not catch, including during test-driven development. Do not generate a comprehensive suite by default. Invoke /writing-tests before changing test setup or assertions.\n\nExamples:\n \nContext: The user has just implemented a…
kingdee-qa-engineer
QA & Test Engineer for the kingdee-mcp project. Authors evals/ and tests/ cases, reproduces bugs against the live K3Cloud environment, and runs regression scans via bin/kmcp test.
integ-test-runner
Runs integ-test-playbook.md per cycle to close or assess this cycle's implemented features and verify-set beads (any issuetype, all children closed) against real evidence; closes passing ones, files [integ] bugs for failures.
debug-investigator
Bug diagnosis and fix specialist. Error analysis, root cause identification, regression test writing.
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.