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/generate-commands)<a href="https://agentmods.dev/commands/arrrrny/zuraffa/generate-commands"><img src="https://agentmods.dev/badge/commands/arrrrny/zuraffa/generate-commands.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.00020 | $0.00212 |
| Opus 5 | $0.00010 | $0.00106 |
| Sonnet 5 | $0.00004 | $0.00042 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
speckit.zuraffa.generate-commands 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 3d 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.
What it actually says
Generate Commands: Regenerate all extension command files from zfa manifest
Usage
zfa generate-commands
When to Use
Regenerate all extension command files from zfa manifest
Required Parameters
- name: Name of the target (e.g. Product)
Flags
| Flag | Type | Required | Default | Description |
|---|---|---|---|---|
--name |
string | No | - | Name of the target (e.g. Product) |
--force |
bool | No | False | Force overwrite existing files |
--dry-run |
bool | No | False | Preview without writing files |
--verbose |
bool | No | False | Enable verbose logging |
Output
Supports --dry-run to preview without writing files.
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.
- 3d ago First seen · 35 lines · 20 tokens per session scan A 4cfa610b6874
speckit.zuraffa.generate-commands is a command published in the GitHub repository arrrrny/zuraffa (5 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 212 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-09-03.
Other commands, from other repositories
building-flutter-apps-skill-ac1294fc
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.
deep-link
Configuration Deep Linking React Native.
generate-screen
Génération Screen React Native.
status
Show tlive daemon, channel, and Codex companion status.
native-analyze
Fingerprint and analyze a native Android library (or a whole arm64-v8a directory) with revx.
design-mobile
Design a mobile screen or flow. This command never writes SwiftUI or Compose — the deliverable is a device-framed HTML mockup plus a handoff spec for the platform developer.