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/joaquimscosta/arkhe-claude-pluginsWrote 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/joaquimscosta/arkhe-claude-plugins/research)<a href="https://agentmods.dev/commands/joaquimscosta/arkhe-claude-plugins/research"><img src="https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/research/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/joaquimscosta/arkhe-claude-plugins/research"><img src="https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/research.svg" alt="Reviewed on agentmods" width="80" 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.00036 | $0.00541 |
| Opus 5 | $0.00018 | $0.00270 |
| Sonnet 5 | $0.00007 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
research 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 9d 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
Research
Arguments: $ARGUMENTS
Scripts: Glob for **/deep-research/scripts/cache_manager.py and use its parent directory as {scripts}.
Dispatch
Parse arguments to determine the operation:
Research (default — no keyword prefix)
Cache-first approach using a single fetch call:
- Run:
python3 {scripts}/cache_manager.py fetch "{topic}" - Parse the JSON output:
exists=true,cache_status=valid: Present thecontentfield to the user. Report cache HIT, path, expiration. Suggest/research promote {slug}.exists=true,expired=true: Present thecontentfield. Warn: "Cache expired — returning cached content." Suggest/research refresh {slug}. Do NOT spawn agent.exists=false: Spawndeep-researcheragent (subagent_type:core:deep-researcher). Pass the topic andscriptspath so the agent can cache results viacache_manager.py put.
Promote (promote <slug>)
- Run:
python3 {scripts}/promote.py {slug} - Parse JSON output. Report success path or error.
Refresh (refresh <slug>)
- Spawn
deep-researcheragent (subagent_type:core:deep-researcher). - Instruct it to: bypass cache, research fresh via EXA, cache with
cache_manager.py put, then runpromote.py {slug} --refreshifdocs/research/{slug}.mdexists.
List (list [--all | --project <name>])
- Run:
python3 {scripts}/cache_manager.py list --format json [--all | --project <name>] - Scan
docs/research/for promoted entries. - Display as formatted markdown table with Cached (Tier 1) and Promoted (Tier 2) sections.
Cache Tiers
- Tier 1 (User):
~/.claude/plugins/research/— cross-project, 30-day TTL - Tier 2 (Team):
docs/research/— version controlled, editable
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.
- 9d ago First seen · 49 lines · 36 tokens per session scan A 2a8501b72ee3
research is a command published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed 25d ago), licensed MIT. It adds 36 tokens to every session and 541 once invoked, about $0.0002 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-30.
Other commands, from other repositories
stats
Show real token usage, delegation rate, and actual savings for the current Hydra session (parses Claude Code session JSONL — no AI estimation).
permissions
Create or update DOGMA-PERMISSIONS.md to configure what Claude can do autonomously.
merge
You are executing the /hydra:merge command. Merge a worktree branch back into the current branch.
parallel
You are executing the /hydra:parallel command. Start multiple agents simultaneously in different worktrees.
sandbox-promote
Promote an accepted, version-worthy WIP artifact from .credo/sandbox-tmp/ / to .credo/sandbox/ /. is the sandbox-tmp folder name (argument: $1).
add-skill
Add a new Skill to the current plugin with proper structure.