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 ribeirogab/specwright --skill implementgit clone --depth 1 https://github.com/ribeirogab/specwrightWrote 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/ribeirogab/specwright/implement)<a href="https://agentmods.dev/skills/ribeirogab/specwright/implement"><img src="https://agentmods.dev/badge/skills/ribeirogab/specwright/implement/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/ribeirogab/specwright/implement"><img src="https://agentmods.dev/badge/skills/ribeirogab/specwright/implement.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.00079 | $0.01466 |
| Opus 5.5 | $0.00032 | $0.00586 |
| Sonnet 5.5 | $0.00016 | $0.00293 |
| Haiku 4.5 | $0.00008 | $0.00147 |
Grade A, and why
implement scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
one. A session that degrades a UI check to `curl` records the capability gap How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
implement — execute the plan
Take a change folder — proposal.md, tasks.md, and design.md when the scope
called for one — and build what they describe. This skill is designed to run
cold: a fresh session, a different model, a different host, with no memory of
the conversation that produced the plan. Those files are the entire input.
Announce at start: "Implementing the plan."
Locate the change
$ARGUMENTS names a change folder or slug → use it. Otherwise list the changes
in .specwright/changes/*/ whose proposal.md says status: pending or
in-progress and ask which one; a single candidate may be used directly.
Read every file in the folder completely before touching code. Check out the
branch named in tasks.md's branch: frontmatter, creating it from the default
branch if it does not exist yet, and set status: in-progress in proposal.md.
A folder with no design.md is not incomplete: a low-scope change carries its
constraints in tasks.md and needs nothing more. A missing tasks.md is a stop —
the change has no plan yet, and writing one is /sw:plan's job, not this
skill's.
Never work on the default branch
After the checkout and before the first commit:
git branch --show-current
If it is main or master — because branch: names it, because the checkout
did not happen, or because the frontmatter is blank — stop. Report the branch
this change should be on and let the maintainer create it. Do not commit, and do
not pick a branch name on their behalf.
This gate runs once, here, and it is the only thing standing between an unattended run and a series of commits on the default branch.
Resume from the checkboxes
The checkboxes in tasks.md are the state. Find the first unticked step and
start there — everything above it is done, whoever did it. Never restart a task
whose boxes are ticked, and never re-derive progress from the git log; the file
is the record.
Before starting, confirm the working tree is clean. Uncommitted work from a previous run is ambiguous: report it and let the maintainer resolve it rather than committing or discarding on their behalf.
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.
- 1mo ago First seen · 135 lines · 79 tokens per session scan A 7c2477a2a24f
implement is a skill published in the GitHub repository ribeirogab/specwright (3 stars, last pushed 2mo ago), licensed MIT. It adds 79 tokens to every session and 1,466 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
template-sia
SIA (Self-Improvement Agent) harness exemplar — Meta/Target/Feedback loops, public/private splits, fixture replay, fail-closed validation.
review-depth
Decide how much review a change has earned, before reviewing it. Selects quick, standard, or deep from stated signals (reviewable changed lines, directory spread, trust-boundary risk flags, blast radius, documentation-only scope), reports the signal table and the rule that fired, then runs house-review at the selected…
systematic-debugging
Use when a defect, test failure, flaky test, or unexpected behavior needs its cause established before anyone writes a task file or a fix. Reproduces the report first, localizes the failure to the boundary where behavior diverges, then tests one hypothesis at a time and returns a deterministic verdict, so a run that…
doc-sync
Use when code has moved and the documentation may not have, or when a documentation set needs auditing for stale claims. Detects documentation drift by checking prose claims against repository facts, classifies every document as current-state (correctable), contract (report-only, human-owned) or ledger (skipped), and…
init-worktracking
Scaffold a portable, agent-optimized spec-driven work-tracking system into the current repository: AGENTS.md (global rules + agent reading protocol), a .tasks/ directory of atomic task files, and (by tier) ROADMAP.md, CHANGELOG.md, a validate.py checker, and thin CLAUDE.md/Cursor/Copilot pointers. Choose a footprint…
reconcile-worktrees
Safely consolidate one or more isolated git worktrees (for example left behind by parallel background agents, or from the fix-batch skill) into the main working tree, without committing or merging blindly. Use whenever asked to "reconcile the worktrees", "merge these agent branches", "bring the worktree changes back…