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 skills add martinffx/atelier --skill spec-brainstormgit clone --depth 1 https://github.com/martinffx/atelierWrote 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/skills/martinffx/atelier/spec-brainstorm)<a href="https://agentmods.dev/skills/martinffx/atelier/spec-brainstorm"><img src="https://agentmods.dev/badge/skills/martinffx/atelier/spec-brainstorm/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/skills/martinffx/atelier/spec-brainstorm"><img src="https://agentmods.dev/badge/skills/martinffx/atelier/spec-brainstorm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00095 | $0.03249 |
| Opus 5.5 | $0.00038 | $0.01300 |
| Sonnet 5.5 | $0.00019 | $0.00650 |
| Haiku 4.5 | $0.00010 | $0.00325 |
Grade A, and why
spec-brainstorm 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 11d 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 — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Brainstorm
Conversational design workshop for substantial work that produces a focused, reviewed spec.
One question at a time. Multiple approaches explored. Design approved in sections. Ruthless scope control. No implementation until design is approved.
Run this skill only after atelier-orchestrator selects a Spec-backed Plan or the human
explicitly requests a spec. Bounded work should go directly to spec-plan for an Inline
Plan. Do not reclassify the planning mode here.
Artifact
docs/specs/YYYY-MM-DD-<feature>/
└── design.md ← This skill's output
Requirements are inline — no separate requirements.json needed.
Exclusive output contract
This skill may create or update only the design.md shown above. It may inspect the
repository and discuss drafts in conversation, but it must not modify any other file, create
plan.json, create tracker entries, invoke another workflow skill, or write implementation
code. This boundary still applies when the human asks to brainstorm, plan, and implement in
one request. Finish design.md, report it, and stop.
Lessons
These principles apply to every spec, every time.
Specs must earn their cost
Persisted specs are for work whose discovery, architecture, dependencies, or coordination needs justify a durable artifact. Do not pull bounded work into this workflow merely because it touches multiple files or takes time. That work belongs in an Inline Plan.
Design for isolation and clarity
Break the system into units with one clear purpose each. Well-defined interfaces between them. Each unit independently understandable and independently testable. If you can't explain a unit's job in one sentence, it's doing too much. Apply oracle-codebase-design: deep modules, seams placed where behaviour varies, and the interface as the test surface.
Working in existing codebases
Explore the current structure first. Follow existing patterns. Targeted improvements only. No unrelated refactoring. Understand why things are the way they are before proposing changes. Treat loaded skills as relevant guidance, not as a requirement to apply every pattern they contain.
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.
- 11d ago Changed · +7 lines 83e6272376d6
- 1mo ago First seen · 385 lines · 95 tokens per session scan A d17b2f7654b2
spec-brainstorm is a skill published in the GitHub repository martinffx/atelier (48 stars, last pushed 3d ago), licensed MIT. It adds 95 tokens to every session and 3,249 once invoked, about $0.0004 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-30.
Other skills, from other repositories
harbor
Harbor intake for external work — the captain only handles unresolved decisions. Sweeps incoming issues and PRs, verifies every claim before disposition, reuses every decision already made, and hands the maintainer a docket whose pending items each carry one question with options, recommendation, impact and evidence.…
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
omc-review
Evaluate finished work for defects, risk, and simplification before it ships.
tech-debt-collector
Evidence-gated tech debt and bloat detection. Scouts signals, ranks by materiality, validates by refutation, reports up to 5 findings with actions.
pr-review
Intent-aware map-reduce PR review with CI/CD support, confidence gating, and intelligent comment deduplication.
pr-walkthrough
Generate an evidence-grounded markdown walkthrough for a pull request.