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/agents/joaquimscosta/arkhe-claude-plugins/agent-template)<a href="https://agentmods.dev/agents/joaquimscosta/arkhe-claude-plugins/agent-template"><img src="https://agentmods.dev/badge/agents/joaquimscosta/arkhe-claude-plugins/agent-template/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/agents/joaquimscosta/arkhe-claude-plugins/agent-template"><img src="https://agentmods.dev/badge/agents/joaquimscosta/arkhe-claude-plugins/agent-template.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.00039 | $0.00167 |
| Opus 5.5 | $0.00016 | $0.00067 |
| Sonnet 5.5 | $0.00008 | $0.00033 |
| Haiku 4.5 | $0.00004 | $0.00017 |
Grade A, and why
agent-name 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 2d 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
You are a specialized [ROLE] assistant with expertise in [DOMAIN].
Core Capabilities
- [Capability 1]
- [Capability 2]
- [Capability 3]
Approach
- [Step 1 of your methodology]
- [Step 2 of your methodology]
- [Step 3 of your methodology]
Quality Standards
- [Standard 1]
- [Standard 2]
- [Standard 3]
Output Format
[Describe expected output format and structure]
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.
- 2d ago First seen · 31 lines · 39 tokens per session scan A 06a0035de9c6
agent-name is an agent published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 167 once invoked, about $0.0002 per session on Opus 5.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-10-16.
Other agents, from other repositories
hydra-scout
🟢 Hydra's fastest head — ultra-fast codebase exploration, information retrieval, and codebase map building/maintenance. Use proactively whenever Claude needs to search files, read code, find patterns, grep for strings, list directories, understand project structure, answer "where is X?" questions, or build/update the…
hydra-runner
🟢 Hydra's execution head — fast test runner, build executor, and validation agent. Use proactively whenever Claude needs to run tests, execute builds, check linting, verify formatting, run type checks, check git status, execute simple scripts, or validate that changes work. Runs on the cheap tier for speed — ideal…
code-reviewer
PROACTIVELY use after code changes to review for security, performance, correctness, and maintainability. Reads diffs, analyzes patterns, reports issues by severity. Does not modify code.
agent-critic
Use this agent when you need a plugin-aware review of one or more agent definitions — the .md files under a plugin's agents/ directory. Adapts the plugin-dev agent-development skill methodology and reports findings in the fakoli-plugin-critic severity rubric (MUST FIX / SHOULD FIX / CONSIDER / NIT). Agent-critics…
security-master
Use this agent when dealing with any security-relevant question, decision, or implementation. This includes authentication and authorization design, data privacy and DSGVO/GDPR compliance, dependency audits, threat modeling, security hardening, infrastructure security, and release readiness checks. This agent MUST be…
perf-orchestrator
Coordinate /perf investigations across all phases, enforcing non-negotiable perf rules.