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 benjaminthomas/spec-driven-dev --skill spec-investigategit clone --depth 1 https://github.com/benjaminthomas/spec-driven-devWrote 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/benjaminthomas/spec-driven-dev/spec-investigate)<a href="https://agentmods.dev/skills/benjaminthomas/spec-driven-dev/spec-investigate"><img src="https://agentmods.dev/badge/skills/benjaminthomas/spec-driven-dev/spec-investigate/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/benjaminthomas/spec-driven-dev/spec-investigate"><img src="https://agentmods.dev/badge/skills/benjaminthomas/spec-driven-dev/spec-investigate.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.00213 | $0.04290 |
| Opus 5.5 | $0.00085 | $0.01716 |
| Sonnet 5.5 | $0.00043 | $0.00858 |
| Haiku 4.5 | $0.00021 | $0.00429 |
Grade A, and why
spec-investigate 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 yesterday.
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 — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spec-investigate
Discover and record the facts. Do not design the fix and do not write any code.
This skill is stage 1 of:
spec-investigate → spec-create → human approval → spec-implement → spec-verify → spec-ship
spec-create, spec-implement, spec-verify, and spec-ship already exist elsewhere (e.g. the
spec-driven-dev plugin, or whatever equivalent this host provides). Never create, redesign,
duplicate, or invoke those skills from here. Your only output is an investigation report plus a
ready-to-use work branch; a human decides when to run spec-create next.
Project config (read first)
Load .spec-driven.yml: walk up from the current directory to the home folder, and the first one
found wins (a multi-repo config only applies inside the repos it lists). If none is found, check
~/.spec-driven/workspaces.json, which maps each multi-repo config to its repo paths. Use the config
whose repos contain the current directory, because a workspace's repos can live in unrelated folders. Its values beat anything
you would detect or assume. This skill uses layout/repos (where to look and what each repo does), tracker, git.remote, git.base_branch, git.branch_name, and specs_dir.
Monorepo: name the package(s) involved. Multi-repo: search every listed repo whose role fits the ticket, and create the work branch, with the same name, only in the repos the investigation shows need changes.
No config? If the spec-setup skill is available, run it first, then continue here. If it
isn't, detect what this skill needs from the repo, ask about anything ambiguous, and offer to save
the answers to .spec-driven.yml (keys: layout, repos, tracker, git, commands,
specs_dir).
Invocation
spec-investigate STP-123
spec-investigate https://<org>.atlassian.net/browse/STP-123
spec-investigate STP-123 --context ./notes.md
spec-investigate #482 # GitHub issue in the current repo
spec-investigate https://github.com/<owner>/<repo>/issues/482
spec-investigate https://linear.app/<team>/issue/ENG-91
spec-investigate ./call-transcript.txt # transcript, notes, PRD, RFC, log — any file
spec-investigate "Checkout times out for EU users since Tuesday's deploy" # plain text
spec-investigate # with the material pasted in the same message
What ships with it
1 file 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.
- yesterday First seen · 331 lines · 213 tokens per session scan A f01f7a4b5b03
spec-investigate is a skill published in the GitHub repository benjaminthomas/spec-driven-dev (2 stars, last pushed 2d ago), licensed MIT. It adds 213 tokens to every session and 4,290 once invoked, about $0.0009 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-11-07.
spec-investigate compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| spec-investigatebenjaminthomas/spec-driven-dev | Skill | 2 | 2d ago | MIT | A | 213 | Claude Code |
| cloud-logging-query-generationhamzabellouch/agent-skills | Skill | 8 | 22d ago | MIT | A | 67 | Claude Code, Codex |
| datalineage-summaryhamzabellouch/agent-skills | Skill | 8 | 22d ago | MIT | A | 92 | Claude Code, Codex |
| browser-testing-with-devtoolshamzabellouch/agent-skills | Skill | 8 | 22d ago | MIT | B | 68 | Claude Code, Codex |
| doubt-driven-developmentaddyosmani/agent-skills | Skill | 114k | 6d ago | MIT | A | 96 | Claude Code |
| performance-optimizationaddyosmani/agent-skills | Skill | 114k | 6d ago | MIT | A | 59 | Claude Code |
| bug-fix-protocolCodeAlive-AI/ai-driven-development | Skill | 169 | today | MIT | A | 94 | Claude Code |