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 skills/qgolem/orc/orc-generatenpx skills add qGolem/orc --skill orc-generategit clone --depth 1 https://github.com/qGolem/orcWrote 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/qgolem/orc/orc-generate)<a href="https://agentmods.dev/skills/qgolem/orc/orc-generate"><img src="https://agentmods.dev/badge/skills/qgolem/orc/orc-generate.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 | $0.00017 | $0.02427 |
| Opus 5 | $0.00009 | $0.01213 |
| Sonnet 5 | $0.00003 | $0.00485 |
| Haiku 4.5 | $0.00002 | $0.00243 |
Grade A, and why
orc-generate 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orc Generate
Thin orchestrator for plan generation. Owns the workflow loop — delegates ALL planning methodology to thick agents (orc-planner, orc-plan-checker).
Input
- $ARGUMENTS — Plan slug
Templates
- templates/ROADMAP.md — Phase tracking
Execution
Step 0: Initialize Todos
Step 1: Load Context
Read:
.claude/plans/$ARGUMENTS/PROJECT.md— vision.claude/plans/$ARGUMENTS/STATE.md— codebase findings.claude/plans/$ARGUMENTS/research/SUMMARY.md— domain research synthesis (if exists)
Step 2: Design Phase Breakdown
Analyze PROJECT.md and STATE.md to design phases:
- Atomic tasks per phase
- Each phase independently verifiable
- Order: dependencies → core → enhancements
Step 3: Validate with User
Present your proposed phase breakdown and ask for feedback:
Based on the vision and codebase analysis, here's my proposed phase breakdown:
**Phase 1: <name>**
- Task 1.1: <brief description>
- Task 1.2: <brief description>
**Phase 2: <name>**
- Task 2.1: <brief description>
- Task 2.2: <brief description>
**Phase 3: <name>** (if needed)
- Task 3.1: <brief description>
...
for each phase:
**Phase N: <name>**
- Task N.1: <brief description>
Please review and let me know:
1. Does this breakdown make sense for your priorities?
2. Should any phases be combined, split, or reordered?
3. Before planning starts, would you like to discuss or research any specific phase?
Run `/orc-discuss $slug N` or `/orc-phase-research $slug N` standalone, then tell me to proceed.
4. Is anything missing or unnecessary?
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 281 lines · 17 tokens per session scan A 7269c1395e10
orc-generate is a skill published in the GitHub repository qGolem/orc (5 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 2,427 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
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
status
Where is the work right now. Regenerates the projections and the kanban board from the journal and answers with the progress line, the agents still running, the open gates and the resume steps. Read-only. Use for /tyran:status or when asked what is going on.
prompt-tuning
Tune a prompt, or anything whose quality is measured by non-deterministic model output, without chasing noise - a noise baseline before the first edit, medians over repeated runs, enforcement AFTER generation rather than in the wording. Use when iterating on prompts or model-judged output.
brainstorm
Explores a codebase, researches the problem space, and produces an approved design specification before any code is written. Use when the user wants to create a new feature, add significant functionality, redesign a subsystem, or build something that touches multiple parts of the project.
a11y-audit
Dedicated WCAG 2.2 AA/AAA accessibility audit across 10 dimensions (A1-A10) covering semantic HTML, keyboard navigation, ARIA patterns, color contrast, forms, images/media, responsive/zoom, motion/animation, reading/content, and legal compliance. Goes far beyond surface-level design-review checks with deep…
api-audit
API and endpoint integrity audit across 10 dimensions (D1-D10) plus optional contract stability (D11) and optional OWASP API Security Top 10 (D12: BOLA/BOPLA/BFLA, mass assignment, JWT alg-confusion, GraphQL introspection). Covers validation, payloads, pagination, errors, caching, HTTP semantics, waterfalls, rate…