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 agentmods add commands/jircdev/crew-plugin/crewgit clone --depth 1 https://github.com/jircdev/crew-pluginWhat 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 | $0.00015 | $0.00134 |
| Opus 5 | $0.00008 | $0.00067 |
| Sonnet 5 | $0.00003 | $0.00027 |
| Haiku 4.5 | $0.00002 | $0.00013 |
Grade A, and why
crew 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 yesterday.
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
Spawn the crew subagent for the following task. Operate strictly within that role's Authority and Scope as defined in the role document. Default to a conversational reply scoped exactly to what was asked. Produce the role's canonical Deliverable only when the user explicitly asks for a brief, spec, or document, or when the conversation has converged on a decision and writing it up is the next step. Do not drift into other roles — if the task requires a different role, say so and stop.
Task: $ARGUMENTS
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.
- yesterday First seen · 9 lines · 15 tokens per session scan A f3d0ad08d5dc
crew is a command published in the GitHub repository jircdev/crew-plugin (2 stars, last pushed 12d ago), licensed MIT. It adds 15 tokens to every session and 134 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
verify
Adversarial spec-vs-implementation verification for a completed task. Dispatches the spec-mentor subagent with fresh context (no anchoring bias), parses its verdict (PASS / DRIFT / NEEDS-MARTY), and updates the verification queue. The v7.4.0 architectural replacement for a dedicated "mentor session.".
research
Enter RESEARCH mode for information gathering.
criar-skill
Use when creating new skills, automations, or specialized knowledge packages. Keywords: criar skill, nova skill, automatizar, conhecimento, TDD skill.
research
Delegate a thorough research investigation to the agy:runner subagent.
station
You are helping the user work with Station - the self-hosted AI agent orchestration platform.
delegate
Delegate investigation, an explicit fix request, or follow-up work to the Grok delegate subagent.