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 arrrrny/zuraffa --skill speckit-chore-implementgit clone --depth 1 https://github.com/arrrrny/zuraffaWrote 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/arrrrny/zuraffa/speckit-chore-implement)<a href="https://agentmods.dev/skills/arrrrny/zuraffa/speckit-chore-implement"><img src="https://agentmods.dev/badge/skills/arrrrny/zuraffa/speckit-chore-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/arrrrny/zuraffa/speckit-chore-implement"><img src="https://agentmods.dev/badge/skills/arrrrny/zuraffa/speckit-chore-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.00022 | $0.01847 |
| Opus 5 | $0.00011 | $0.00924 |
| Sonnet 5 | $0.00004 | $0.00369 |
| Haiku 4.5 | $0.00002 | $0.00185 |
Grade A, and why
speckit-chore-implement 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Chore
Apply the maintenance work that was scoped by /speckit-chore-assess and record the changes in an implement report at .specify/chores/<slug>/implement.md. This command is only valid after an assessment exists for the given slug. Pass --branch (or --worktree) to isolate the chore on its own git branch before editing, mirroring how /speckit-specify isolates feature work.
User Input
$ARGUMENTS
The user input should identify the chore to implement. Accept any of:
slug=<chore-slug>or--slug <chore-slug>or just a bare slug-like token.- A path that contains the slug (e.g.
.specify/chores/logo-swap/). - Branch isolation (optional):
branch/--branchcreates a chore branch (<prefix>/<slug>) first;worktree/--worktreecreates a git worktree instead. See Optional — isolate the chore on a branch below. - Nothing — fall back to context (see below).
Slug Resolution
Resolve CHORE_SLUG in this order, stopping at the first match:
- Explicit user input — a slug passed in
$ARGUMENTS(any of the forms above). - Conversation context — if the current session has just run
/speckit-chore-assess, the slug it reported is the working slug. Reuse it without re-prompting. Confirm it by checking that.specify/chores/<slug>/assessment.mdexists; if it does not, fall through. - Single candidate on disk — list
.specify/chores/*/assessment.md. If exactly one matchingassessment.mdis found, use the slug from its parent directory. - Disambiguate:
- Interactive mode: ask the user which chore to implement and list the candidates.
- Automated mode: stop with an error listing the candidates. Do not guess.
Once resolved, set CHORE_SLUG and CHORE_DIR = .specify/chores/<CHORE_SLUG>, and briefly state in your reply which resolution path was used (explicit / from context / single candidate / asked).
Prerequisites
CHORE_DIR/assessment.mdMUST exist. If it does not, stop and instruct the user to run/speckit-chore-assessfirst.- If
CHORE_DIR/implement.mdalready exists, ask the user whether to overwrite it before continuing (interactive mode) or refuse (automated mode). - Read
CHORE_DIR/assessment.mdin full. Treat its Proposed Approach, Paths likely to change, Verification to run, Constitution Check, and Risks & Considerations sections as the contract for this command.
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.
- 5d ago Changed · -126 lines · -22 tokens per session 5c32f03336a3
- 9d ago First seen · 127 lines · 22 tokens per session scan A bcf727dd60db
speckit-chore-implement is a skill published in the GitHub repository arrrrny/zuraffa (5 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 1,847 once invoked, about $0.0001 per session on Opus 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-31.
Other skills, from other repositories
flutter
Use when building, structuring, testing or optimizing a Flutter app — feature-first layering, Riverpod 3 or Bloc, typed gorouter, freezed models, a dio data layer, Material 3, jank hunting, widget/golden tests. Targets Flutter 3.44 / Dart 3.12. NOT React Native (that is react-native), NOT Compose Multiplatform (that…
building-flutter-apps
Flutter Riverpod app architecture and Windows installer delivery. Use before changing a Riverpod Flutter app/package or its Windows desktop packaging/update pipeline; skip non-Riverpod stacks and pure-Dart work.
fl-data-layer
Builds the data layer with Freezed DTOs, Retrofit clients, the storage-seam local data manager, and repositories wired through injectable.
fl-route-config
Configures routes with the IRoute / CustomRouter abstractions in core and exposes navigation via a BuildContext coordinator.
fl-bus-event
Handles cross-feature BusEvent communication with EventBusManager in the Flutter base template.
fl-module-scaffold
Scaffolds a new feature module under apps/main/lib/presentation/modules using the bundled module generator.