Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ArtemioPadilla/agent-triforce/plugin install 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/gate)<a href="https://agentmods.dev/commands/artemiopadilla/agent-triforce/gate"><img src="https://agentmods.dev/badge/commands/artemiopadilla/agent-triforce/gate/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/gate"><img src="https://agentmods.dev/badge/commands/artemiopadilla/agent-triforce/gate.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.00000 | $0.00393 |
| Opus 5 | $0.00000 | $0.00197 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
gate 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.
What it actually says
View, create, approve, or override approval gates between agents.
Gates enforce formal approval checkpoints in the Agent Triforce workflow:
- plan-gate: Prometeo approves Forja's implementation plan before coding begins
- release-gate: Centinela signs off before a feature is released
Usage
Check gate status
/gate check --feature {feature-name} --gate-type {plan-gate|release-gate}
Create a new gate
/gate create --feature {feature-name} --gate-type {plan-gate|release-gate} --criteria "Criterion 1" --criteria "Criterion 2"
Approve a gate
/gate approve --feature {feature-name} --gate-type {plan-gate|release-gate} --approved-by "{agent or user}"
Override a gate (requires reason)
/gate override --feature {feature-name} --gate-type {plan-gate|release-gate} --override-reason "Reason for override"
Gate Documents
Gate documents are stored at docs/gates/{feature-name}-{gate-type}.md. They are permanent artifacts (not gitignored) and serve as the audit trail.
Behavior
Run the appropriate gate-checker.py subcommand based on the user's request. If no subcommand is clear from the user's message, run check to show the current gate status.
When the user asks to view or check a gate, run:
python3 ${CLAUDE_PLUGIN_ROOT}/tools/gate-checker.py check --feature {feature} --gate-type {type}
When the user asks to create, approve, or override a gate, run the corresponding subcommand.
Display the JSON output in a readable format. For check results, highlight whether the gate PASSED or is BLOCKED.
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 · 45 lines · 0 tokens per session scan A acdb6f624a6d
gate is a command published in the GitHub repository ArtemioPadilla/agent-triforce (3 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 393 tokens. 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
dashboard
Starts the live web dashboard for the current fellowship — quest/scout progress, gate approvals, and event history — in the background, and prints the URL.
mega-status
Show detailed status of mega-plan execution including feature progress and story completion. Usage: /plan-cascade:mega-status.
hybrid-status
Show execution status of all stories in the PRD. Displays batch progress, individual story states, completion percentage, and recent activity logs.
hybrid-complete
Complete Hybrid Ralph task in worktree, verify all stories complete, commit code changes (excluding planning files), merge to target branch, and cleanup worktree directory. Can be run from any directory.
OPSX: Fast Forward
Create a change and generate all artifacts needed for implementation in one go.
OPSX: Bulk Archive
Archive multiple completed changes at once.