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.
git 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/commands/arrrrny/zuraffa/speckit.chore.issue)<a href="https://agentmods.dev/commands/arrrrny/zuraffa/speckit.chore.issue"><img src="https://agentmods.dev/badge/commands/arrrrny/zuraffa/speckit.chore.issue.svg" alt="Measured on agentmods" 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.00021 | $0.01510 |
| Opus 5 | $0.00010 | $0.00755 |
| Sonnet 5 | $0.00004 | $0.00302 |
| Haiku 4.5 | $0.00002 | $0.00151 |
Grade A, and why
speckit.chore.issue 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 8d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report Chore (Create Issue)
Turn a local chore assessment into a tracked GitHub issue. This command reads
.specify/chores/<slug>/assessment.md (produced by
__SPECKIT_COMMAND_CHORE_ASSESS__) and creates a GitHub issue via the gh CLI,
then records the issue number and URL in CHORE_DIR/issue.md. If gh or a GitHub
remote is unavailable, it writes a ready-to-paste draft instead so no work is lost.
User Input
$ARGUMENTS
Accept any of:
slug=<chore-slug>or--slug <chore-slug>or a bare slug-like token.- A path that contains the slug (e.g.
.specify/chores/logo-swap/). - Nothing — fall back to context (see Slug Resolution).
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_COMMAND_CHORE_ASSESS__, the slug it reported is the working slug. Reuse it without re-prompting. - 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 report 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>.
Prerequisites
CHORE_DIR/assessment.mdMUST exist. If it does not, stop and instruct the user to run__SPECKIT_COMMAND_CHORE_ASSESS__first.- Read
CHORE_DIR/assessment.mdin full. Treat its Summary, Affected Paths, Proposed Approach, Constitution Check, and Source fields as the basis for the issue. - Detect GitHub context:
- Run
git rev-parse --is-inside-work-tree 2>/dev/nullto confirm a repository. - Run
git config --get remote.origin.urlto read the remote. Parseownerandrepo(HTTPShttps://github.com/<owner>/<repo>.gitor SSH[email protected]:<owner>/<repo>.git). Only proceed with issue creation when the remote points togithub.com. - Check for
ghwithcommand -v gh >/dev/null 2>&1. If absent, or the remote is not GitHub, or the user is not authenticated (gh auth statusfails), skip live creation and write a draft (see Graceful Degradation).
- Run
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.
- 8d ago First seen · 101 lines · 21 tokens per session scan A b9f3723e493d
speckit.chore.issue is a command published in the GitHub repository arrrrny/zuraffa (5 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 1,510 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 commands, from other repositories
auto-sprint
Orchestrateur de sprint de bout en bout (démarrage -> décomposition -> validation -> implémentation -> PR -> CI -> revue -> rétro -> merge).
review
Préparation Sprint Review.
afcl
Close feature [agent] [--adopt] - merges branch, cleans up, optionally adopts from losers (shortcut for feature-close).
next
Suggest the most likely next workflow action based on current context.
update-check.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
aft
Transfer feature from its current agent to a different agent — preserves commits and in-flight work (shortcut for feature-transfer).