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/methodology)<a href="https://agentmods.dev/commands/artemiopadilla/agent-triforce/methodology"><img src="https://agentmods.dev/badge/commands/artemiopadilla/agent-triforce/methodology/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/artemiopadilla/agent-triforce/methodology"><img src="https://agentmods.dev/badge/commands/artemiopadilla/agent-triforce/methodology.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.00009 | $0.01105 |
| Opus 5 | $0.00005 | $0.00553 |
| Sonnet 5 | $0.00002 | $0.00221 |
| Haiku 4.5 | $0.00001 | $0.00111 |
Grade A, and why
methodology 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Triforce — Checklist Methodology
This system applies principles from The Checklist Manifesto (Atul Gawande) and Boeing's checklist engineering (Daniel Boorman).
Core Philosophy
- Ineptitude, not ignorance: Failures come from not applying what we already know
- Checklists supplement expertise: Reminders of the most critical steps — not comprehensive how-to guides
- FLY THE AIRPLANE: Step 1 of any emergency is to remember your primary mission
- Discipline is professionalism: Consulting a checklist, no matter how experienced you are, is what separates reliable systems from fragile ones
Checklist Design Rules (Boorman's Principles)
- Clear pause point: A specific moment where you STOP and consult the checklist
- 5-9 killer items only: The steps most dangerous to skip
- Under 60 seconds: If it takes longer, it will be skipped
- Simple, exact wording: Concrete, verifiable actions
- DO-CONFIRM or READ-DO: Every checklist declares its type
- Field-tested and updated: Evolve based on actual failures
Two Checklist Types
- DO-CONFIRM: Do your work, then PAUSE and run the checklist to confirm nothing was missed
- READ-DO: Read each item and do it step by step
Three Pause Points (WHO Surgical Safety Model)
Every agent invocation has three mandatory pause points:
- SIGN IN (DO-CONFIRM): Before starting. State identity, role, task, concerns. Read memory and relevant docs.
- TIME OUT (varies): Mid-workflow verification. Stop, run the checklist, fix failures before proceeding.
- SIGN OUT (DO-CONFIRM): Before finishing. Update memory, confirm deliverables, prepare handoff.
Workflow: Standard Feature Flow
PM SIGN IN → spec → TIME OUT: Spec Completion → SIGN OUT
→ Dev SIGN IN → implement → TIME OUT: Implementation Complete → TIME OUT: Pre-Delivery → SIGN OUT
→ QA SIGN IN → audit → TIME OUT: Security + Quality Verification → SIGN OUT
→ Dev SIGN IN → fix → TIME OUT → SIGN OUT
→ QA SIGN IN → re-verify → SIGN OUT
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 · 97 lines · 9 tokens per session scan A 94a5c1672270
methodology is a command published in the GitHub repository ArtemioPadilla/agent-triforce (3 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 1,105 once invoked, about $0.0000 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.
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.
validate-docs
Validate that site and README documentation is current. Report-only — flags issues without modifying anything.
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.