Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bdfinst/agentic-dev-team/plugin install dev-teamWrote 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/bdfinst/agentic-dev-team/specs)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/specs"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/specs/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/bdfinst/agentic-dev-team/specs"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/specs.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.00089 | $0.03263 |
| Opus 5.5 | $0.00036 | $0.01305 |
| Sonnet 5.5 | $0.00018 | $0.00653 |
| Haiku 4.5 | $0.00009 | $0.00326 |
Grade A, and why
specs 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 14d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent-Assisted Specification
Role: orchestrator. This command produces specification artifacts and gates
progression to /plan — it does not write implementation code, author
per-slice Gherkin scenarios, or begin building.
Positioning — what this skill is for
This skill's value is resolving ambiguity with a human before build begins
(Rec 1, docs/experiments/RECOMMENDATIONS.md). No downstream workflow recovers
information the spec never stated — under vague specs every workflow arm scored
0% on acceptance tests probing an omitted decision. The Ambiguity Resolution
Protocol below is the mechanism: it forces every gap to be either resolved by a
human or documented as inferable before implementation starts.
What this skill is not for: edge-case synthesis. Run to completion, the
full /specs→/plan→/build pipeline's explicit acceptance-criteria
synthesis does not out-perform TDD's failing-test discipline at surfacing
unstated edge cases (25% vs. 33% pooled EDGE pass — Experiment 03, reported in
docs/experiments/02-final-results.md). The two have different failure modes
and both are worth keeping: /specs catches ambiguity a human must resolve;
the build cadence's per-behavior tests catch edge cases the spec implies but
never enumerates.
Step 0 — Select the mode
/specs runs in one of two modes, chosen from the shape of the argument —
there is no flag, so every existing /specs "<description>" invocation is
unaffected. Announce the selected mode and why before any work begins.
| Argument | Mode |
|---|---|
Resolves to a readable .md/.txt/.pdf, or a fetchable GitHub issue URL |
validate — critique a document we did not write |
| Looks like a path or issue URL (a path separator, one of those extensions, or a GitHub issue URL shape) but does not resolve or cannot be fetched | refuse — see below |
| Resembles neither | authoring — today's collaboration loop, unchanged |
A path-like argument that does not resolve is never reinterpreted as prose. Silently feeding a mistyped path into the authoring loop turns a typo into a spec seeded from the literal path string, which the author may not notice for a long time. Refuse instead, naming the unresolved path or the fetch failure (private, deleted, unauthenticated, network).
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 14d ago Changed · +4 lines e1bc058b3d15
- 1mo ago Changed · -7 lines c1730e35a07c
- 1mo ago First seen · 244 lines · 89 tokens per session scan A 22b11d953d9f
specs is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 89 tokens to every session and 3,263 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-09-03.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
remove
Remove a deployed framework or addon from the current workspace.