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/phase-researchnpx skills add qGolem/orc --skill phase-researchgit 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/phase-research)<a href="https://agentmods.dev/skills/qgolem/orc/phase-research"><img src="https://agentmods.dev/badge/skills/qgolem/orc/phase-research.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.00020 | $0.01379 |
| Opus 5 | $0.00010 | $0.00690 |
| Sonnet 5 | $0.00004 | $0.00276 |
| Haiku 4.5 | $0.00002 | $0.00138 |
Grade B, and why
phase-research scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/plans/${slug}/STATE.md How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use this command when:
- You want to research without planning yet
- You want to re-research after planning is complete
- You need to investigate before deciding if a phase is feasible
Orchestrator role: Parse slug + phase, validate against roadmap, check existing research, gather context, spawn researcher agent, present results.
Why subagent: Research burns context fast (WebSearch queries, source verification). Fresh 200k context for investigation. Main context stays lean for user interaction.
Parse slug and phase number in step 0 before any directory lookups.
0. Initialize Context
Parse $ARGUMENTS into slug and phase number:
slug= first wordPHASE= second word
Load project state:
cat .claude/plans/${slug}/STATE.md
Find the phase directory:
ls -d .claude/plans/${slug}/phases/0${PHASE}-*/ 2>/dev/null | head -1
Store as phase_dir. Extract phase_name from the directory name (the part after the number and hyphen).
Check for existing research:
ls ${phase_dir}/RESEARCH.md 2>/dev/null
Store paths for later use:
state_path=.claude/plans/${slug}/STATE.mdproject_path=.claude/plans/${slug}/PROJECT.mdroadmap_path=.claude/plans/${slug}/ROADMAP.mdcontext_path=${phase_dir}/CONTEXT.md(if exists)research_path=${phase_dir}/RESEARCH.md
1. Validate Phase
Read ROADMAP.md and find the phase section:
cat .claude/plans/${slug}/ROADMAP.md
Search for ## Phase ${PHASE}: in the ROADMAP.md content. Extract phase number, phase name, and goal from the section.
If phase not found: Error and exit. If phase found: Continue with extracted details.
2. Check Existing Research
If RESEARCH.md exists: Offer: 1) Update research, 2) View existing, 3) Skip. Wait for response.
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 · 202 lines · 20 tokens per session scan B 981f5c7b456d
phase-research is a skill published in the GitHub repository qGolem/orc (5 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 1,379 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.
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…
debug
Systematic bug investigation with a five-phase framework: reproduce, narrow, diagnose, fix, verify. Supports automated regression bisect via --regression flag. Produces a structured debug report with root cause analysis, regression test, and CQ/Q self-evaluations.