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/team)<a href="https://agentmods.dev/commands/artemiopadilla/agent-triforce/team"><img src="https://agentmods.dev/badge/commands/artemiopadilla/agent-triforce/team/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/team"><img src="https://agentmods.dev/badge/commands/artemiopadilla/agent-triforce/team.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.00014 | $0.00499 |
| Opus 5 | $0.00007 | $0.00249 |
| Sonnet 5 | $0.00003 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
team 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 10d 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
Agent Triforce -- Team Orchestration
Team Configuration
| Role | Agent | Model | Mode |
|---|---|---|---|
| Lead | Prometeo (PM) | sonnet | plan |
| Teammate | Forja (Dev) | inherit | acceptEdits |
| Teammate | Centinela (QA) | sonnet | default |
Orchestration Mode
Default Pipeline: Prometeo -> Forja -> Centinela
When Agent Teams is active, Prometeo acts as team lead and can:
- Delegate implementation tasks to Forja
- Delegate review tasks to Centinela
- Run parallel tasks (e.g., spec feature B while Forja implements feature A)
Parallel Capable: Yes -- agents can work on different features simultaneously.
Inter-Agent Messaging
All handoff messages must include these four fields (from CLAUDE.md Communication Schedule):
- What was done: Summary of work completed
- What to watch for: Known risks, edge cases, concerns
- What's needed next: Explicit expectations for the receiving agent
- Open questions: Anything unresolved that needs the next agent's input
Communication Paths
| From | To | Trigger |
|---|---|---|
| Prometeo | Forja | Spec complete |
| Forja | Prometeo | Spec ambiguity during implementation |
| Forja | Centinela | Implementation complete |
| Centinela | Forja | Review complete |
| Centinela | Prometeo | Business-impacting findings |
| Any agent | User | On ambiguity |
Checklist Discipline
Checklist pause points (SIGN IN / TIME OUT / SIGN OUT) remain mandatory for each agent in team mode. Parallelism does not bypass checklists.
Fallback Mode
If Agent Teams is not available in the Claude Code environment, the system gracefully falls back to sequential single-agent mode. No error is raised -- a single informational message explains that parallel orchestration is unavailable.
Configuration File
Team config: plugins/agent-triforce/team.json
Agent configs: .claude/agents/{prometeo-pm,forja-dev,centinela-qa}.md
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.
- 10d ago First seen · 59 lines · 14 tokens per session scan A cc6f0557b86d
team is a command published in the GitHub repository ArtemioPadilla/agent-triforce (3 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 499 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.