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.fetch)<a href="https://agentmods.dev/commands/arrrrny/zuraffa/speckit.chore.fetch"><img src="https://agentmods.dev/badge/commands/arrrrny/zuraffa/speckit.chore.fetch.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.00016 | $0.02073 |
| Opus 5 | $0.00008 | $0.01037 |
| Sonnet 5 | $0.00003 | $0.00415 |
| Haiku 4.5 | $0.00002 | $0.00207 |
Grade A, and why
speckit.chore.fetch 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 7d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fetch Chore (Load Existing Issue)
Load an existing GitHub issue into the local chore workflow. This is the
complement of __SPECKIT_COMMAND_CHORE_ISSUE__, which creates an issue —
fetch loads one that already exists. It pulls the issue via the gh CLI,
records it at .specify/chores/<slug>/issue.md, and seeds
.specify/chores/<slug>/assessment.md so the rest of the pipeline
(__SPECKIT_COMMAND_CHORE_IMPLEMENT__, __SPECKIT_COMMAND_CHORE_PR__) can proceed.
Use fetch when a chore is already tracked on GitHub (reported by someone else,
or from another session) and you want to scope and implement it here. fetch
never creates, edits, or closes the issue — it only reads it.
User Input
$ARGUMENTS
Accept any of:
- An issue number (e.g.
1234) — resolved against the current repository. - A URL (e.g.
https://github.com/<owner>/<repo>/issues/1234). - An
owner/repo#numberreference (e.g.github/spec-kit#1234). - An explicit slug via
slug=<chore-slug>/--slug <chore-slug>(optional; otherwise derived from the issue title).
Slug Resolution
Each chore gets its own directory under .specify/chores/<slug>/. If the user passed a slug, use it verbatim after normalization (lowercase, hyphen-separated, no spaces, no special characters other than - and digits). Otherwise derive a 2–4 word kebab-case slug from the issue title. Ensure the directory is unique — if .specify/chores/<slug>/ already exists, append the shortest disambiguating suffix (-2, -3, …) or -<issue-number>. Never overwrite an existing chore directory.
After resolution, set CHORE_SLUG and CHORE_DIR = .specify/chores/<CHORE_SLUG>.
Prerequisites
- Ensure
.specify/chores/<CHORE_SLUG>/exists (create it, including any missing parents, if necessary). - If
CHORE_DIR/issue.mdalready exists, do not re-fetch silently: report the existing link and stop (unless the user explicitly asks to refresh). If they ask to refresh, overwriteissue.md; never clobberassessment.md/implement.md— only regenerateassessment.mdif it is missing or with explicit confirmation. - Detect GitHub context (same as
__SPECKIT_COMMAND_CHORE_ISSUE__):git rev-parse --is-inside-work-tree 2>/dev/nullto confirm a repository.git config --get remote.origin.urlto read the remote; parseowner/repo(HTTPShttps://github.com/<owner>/<repo>.gitor SSH[email protected]:<owner>/<repo>.git). Only proceed with a live fetch when the remote points togithub.com.command -v gh >/dev/null 2>&1andgh auth statusto confirm the CLI and auth. Ifgh/GitHub remote/auth is unavailable, skip the live fetch and write a draft (see Graceful Degradation).
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.
- 7d ago First seen · 149 lines · 16 tokens per session scan A cdf0b394709e
speckit.chore.fetch is a command published in the GitHub repository arrrrny/zuraffa (5 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 2,073 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
sdlc
Route a task to the next synced SDLC workflow based on current artifacts and repo state.
workflow-design
Exécuter la phase de Conception (Solutioning) - spécification technique et architecture.
sprint
Équipe de Développement Sprint - Implémentation parallèle de stories utilisant les Agent Teams.
daily-standup
Génération Résumé Daily Stand-up.
adopt-roadmap.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
epic-advance.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.