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 anton-abyzov/specweave --skill sw-grill-megit clone --depth 1 https://github.com/anton-abyzov/specweaveWrote 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/anton-abyzov/specweave/sw-grill-me)<a href="https://agentmods.dev/skills/anton-abyzov/specweave/sw-grill-me"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/sw-grill-me/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/anton-abyzov/specweave/sw-grill-me"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/sw-grill-me.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.00044 | $0.01163 |
| Opus 5.5 | $0.00018 | $0.00465 |
| Sonnet 5.5 | $0.00009 | $0.00233 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
sw-grill-me 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 4d 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.
This is a copy
97% identical to grill-me — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sw-grill-me: settle every decision before building
No one knows exactly what they want. The gap between the user and the agent is where wrong builds come from, and a model never closes it alone: it fills the gaps with guesses. This skill walks the plan's decision tree with the user until nothing is left silently assumed. Use it at a project's start, before a change whose shape is unclear, or whenever the user asks to be grilled. A clear, small request does not need it.
How it runs
- Read first. The code the plan touches,
.specweave/config.json, the open increment's spec.md (specweave task list) andGLOSSARY.mdif it exists. Draft the problem, the scope and the approach yourself. - Map the tree. List every open decision and what it depends on. Probe the things users forget: scope and non-goals; users and flows; the data and the words for it; integrations, installs, accounts and keys; failures and edge cases; security and privacy; performance and scale; rollout and migration; how a machine will check that it works.
- Facts are yours. Anything the code, docs, config or a quick command can answer, look up (in a subagent if your tool has them). Never ask the user what you could find. A lookup still running blocks only the questions that depend on it.
- Ask in rounds. Each round asks the whole frontier: every decision whose prerequisites are already settled. Number the questions; give each one clause on why it matters and your recommended answer, worded so "yes" accepts it. A question that depends on another one in the same round waits for the next round.
- Recompute after every answer: settled decisions unlock new ones, and some answers make others moot. Then ask the next round.
- Stop when the frontier is empty and the user confirms you share one picture. "Enough" or "your call" stops early: every decision left gets your recommendation as a stated default.
Plain text, one round per 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.
- 4d ago First seen · 99 lines · 44 tokens per session scan A d82e962bf5fa
sw-grill-me is a skill published in the GitHub repository anton-abyzov/specweave (166 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,163 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to grill-me, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
bench
GEML is plain text. Every structured thing is one typed block.
project-init
A project-initialization skill that creates a standard starting structure for documentation or software projects. It can add files such as README.md, source, documentation, tests, and project rules.
write-changelog
Generates a CHANGELOG.md entry for a release by summarizing git commits since the last tag. Groups changes by type: Added, Changed, Fixed, Removed. Follows Keep a Changelog format (https://keepachangelog.com). Invoked when the user asks to update the changelog, write release notes, or prepare a release.
write-readme
Generates or updates a README.md for a project or package. Reads the source code to understand the project and produces a clear, accurate README following the project's conventions. Invoked when the user asks to write, update, or generate a README.
doc-summarize
A document-summary workflow for Markdown, plain text, and code documents. It extracts the main points, structure, data, and practical recommendations.
doc-translation
A tool for translating technical documentation while preserving its Markdown structure. Markdown is a plain-text format for headings, lists, links, tables, and code blocks.