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/ArtemioPadilla/agent-triforceWrote 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/artemiopadilla/agent-triforce/setup)<a href="https://agentmods.dev/commands/artemiopadilla/agent-triforce/setup"><img src="https://agentmods.dev/badge/commands/artemiopadilla/agent-triforce/setup.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.1 | $0.00021 | $0.02338 |
| Opus 5 | $0.00010 | $0.01169 |
| Sonnet 5 | $0.00004 | $0.00468 |
| Haiku 4.5 | $0.00002 | $0.00234 |
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 7d 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Triforce — Interactive Setup Wizard
Set up or reconfigure an Agent Triforce project. This wizard detects your tech stack, creates the required directory structure, generates starter files, and optionally configures MCP server connections.
Goal: Go from zero to first spec in under 5 minutes.
Step 1 — Detect Existing Configuration
Check if the project has already been set up:
- Look for existing
CLAUDE.md,docs/directory, and.claude/agents/files - If ALL exist:
- Inform the user: "This project already has an Agent Triforce configuration."
- Ask: "Would you like to (A) reconfigure tech stack preferences only, or (B) run full setup (will not overwrite existing specs, reviews, or memory files)?"
- If reconfigure: skip to Step 3 (tech stack detection), then Step 6 (CLAUDE.md update), then Step 9 (summary)
- If full setup: continue from Step 2 but check before overwriting each file
- If NONE exist: proceed with full setup from Step 2
Step 2 — Create Directory Structure
For each directory below, check if it already exists before creating it. Never overwrite existing content.
Directories:
docs/specs/— feature specifications (Prometeo output)docs/reviews/— QA review reports (Centinela output)docs/adr/— architecture decision records (Forja output)src/— source codetests/— test files
Step 3 — Detect Tech Stack
Scan the project root for manifest files and infer the tech stack:
| File | Stack |
|---|---|
package.json |
Node.js / TypeScript / JavaScript |
pyproject.toml or requirements.txt or setup.py |
Python |
Cargo.toml |
Rust |
go.mod |
Go |
pom.xml or build.gradle |
Java / Kotlin |
Gemfile |
Ruby |
composer.json |
PHP |
*.sol files in project |
Solidity / Web3 |
Additionally detect:
- Framework: Check
package.jsondependencies for Next.js, React, Vue, Express, etc. Checkpyproject.tomlfor FastAPI, Django, Flask, etc. - Test framework: pytest, vitest, jest, mocha, cargo test, go test
- Linter/formatter: ruff, biome, eslint, prettier, rustfmt, gofmt
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.
- 7d ago First seen · 266 lines · 21 tokens per session scan A 8e8b5bd4bd3c
setup is a command published in the GitHub repository ArtemioPadilla/agent-triforce (3 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 2,338 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 commands, from other repositories
settings
View or edit fellowship configuration (/.claude/fellowship.json). Run /settings to see current settings, change values, or reset to defaults.
validate-docs
Validate that site and README documentation is current. Report-only — flags issues without modifying anything.
guide
Interactive guide to fellowship. Walks you through a real task using the structured research-plan-implement flow, then shows you what's next.
rekindle
Recover a fellowship after a session crash. Scans worktrees and quest state, presents a recovery dashboard, and re-spawns Gandalf with recovered quest context. Use when returning to a crashed or expired fellowship session.
chronicle
One-time codebase onboarding — interactively extracts your team's conventions, identifies reference files, and generates CLAUDE.md sections so Claude codes the way your team does. Run once per project.
scribe
Create a reusable quest template for a specific type of task (e.g., "API endpoint", "migration"). Encodes project-specific rules and conventions into phase guidance that loads automatically during quests.