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/setup)<a href="https://agentmods.dev/commands/joaquimscosta/arkhe-claude-plugins/setup"><img src="https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/setup/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/setup"><img src="https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/setup.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.00015 | $0.01467 |
| Opus 5.5 | $0.00006 | $0.00587 |
| Sonnet 5.5 | $0.00003 | $0.00293 |
| Haiku 4.5 | $0.00002 | $0.00147 |
Grade A, and why
setup 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 1mo 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/setup
Purpose: Initialize the Design Intent project structure in your project with smart auto-detection
Usage: /setup
What This Command Does
- Detects Project Configuration - Analyzes package.json, README, .mcp.json, and existing code
- Confirms Settings with User - Individual confirmations for each detected setting
- Creates Directory Structure - Sets up the complete design intent folder hierarchy
- Auto-fills Templates - Intelligently populates templates based on confirmed settings
- Supports Incremental Updates - Re-running updates specific sections without overwriting customizations
Directory Structure Created
your-project/
├── design-intent/
│ ├── memory/
│ │ ├── constitution.md # Core development principles
│ │ ├── team-roles.md # AI/User collaboration expectations
│ │ └── project-vision.md # Your project overview (template)
│ ├── patterns/
│ │ └── design-intent-template.md # Pattern documentation template
│ └── diary/
│ └── session-template.md # Session diary template
Process
1. Check for Existing Setup
If design-intent/ directory already exists, offer incremental update:
Design Intent structure already exists.
What would you like to update?
1. Project vision (preserve customizations)
2. Constitution (merge new framework guidance)
3. Team roles (update MCP capabilities)
4. All templates (reset to defaults)
5. Cancel
2. Detection Phase
Analyze the project to auto-detect configuration:
From package.json:
- Framework (React, Vue, Angular, Next.js)
- Design system (@fluentui/react-components, @mui/material, @chakra-ui/react)
- TypeScript usage
- Key dependencies
From README.md:
- Project description and goals
- Target users mentioned
- Key features
From .mcp.json:
- Figma MCP server configured
- Fluent Pilot MCP configured
- Other relevant MCPs
From existing code:
- Design system component usage patterns
- Styling approach (CSS-in-JS, Tailwind, CSS Modules)
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.
- 1mo ago First seen · 217 lines · 15 tokens per session scan A 32a64e19580f
setup is a command published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed 5d ago), licensed MIT. It adds 15 tokens to every session and 1,467 once invoked, about $0.0001 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-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.
forge-compact-task
Compact context with dotforge-standardized hint that preserves decisions, files modified, pending TODOs, behaviors disabled, and last commit. Use at 80% context window instead of waiting for auto-compact.
recap
Get a summary of everything you learned this session — concepts, quizzes, and progress.
forge-audit
Audit project's Claude Code config and calculate score (0-10).