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/ci-setup)<a href="https://agentmods.dev/commands/artemiopadilla/agent-triforce/ci-setup"><img src="https://agentmods.dev/badge/commands/artemiopadilla/agent-triforce/ci-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.00017 | $0.00767 |
| Opus 5 | $0.00009 | $0.00383 |
| Sonnet 5 | $0.00003 | $0.00153 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
ci-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 8d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up Agent Triforce CI/CD integration for this project. This command explains how to install the GitHub Actions workflow templates.
Available Workflow Templates
Agent Triforce provides 3 GitHub Actions workflow templates in templates/ci/:
1. PR Security Review (pr-review.yml)
- Triggers on: Pull request opened or updated
- What it does: Runs Centinela security review on changed files, posts findings as a PR comment
- Blocks merge if: Critical or High severity findings detected
- Model: Haiku (cost-efficient for routine reviews)
- Timeout: 5 minutes
2. Security Audit (security-audit.yml)
- Triggers on: Push to main branch
- What it does: Runs a full OWASP-focused security audit on changed files
- Output: Saves audit report as a GitHub Actions artifact (90-day retention)
- Model: Haiku
- Timeout: 10 minutes
3. Release Check (release-check.yml)
- Triggers on: Tag push matching
v*(e.g.,v1.0.0) - What it does: Runs the 5-criterion release readiness check (test coverage, security, CHANGELOG, dependencies, tech debt)
- Blocks release if: Verdict is NO-GO
- Output: Attaches go/no-go report to the GitHub release
- Model: Sonnet (higher capability for release decisions)
- Timeout: 10 minutes
Installation Steps
Tell the user to follow these steps:
-
Set up the API key secret:
- Go to your repository Settings > Secrets and variables > Actions
- Create a new repository secret named
ANTHROPIC_API_KEY - Paste your Anthropic API key as the value
-
Copy the workflow files:
mkdir -p .github/workflows cp templates/ci/pr-review.yml .github/workflows/ cp templates/ci/security-audit.yml .github/workflows/ cp templates/ci/release-check.yml .github/workflows/ -
Commit and push:
git add .github/workflows/ git commit -m "ci: add Agent Triforce CI/CD workflows" git push -
Verify: Open a pull request to test the PR review workflow. The security audit runs automatically on the next push to main.
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.
- 8d ago First seen · 75 lines · 17 tokens per session scan A 20f6b4b33179
ci-setup is a command published in the GitHub repository ArtemioPadilla/agent-triforce (3 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 767 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.
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.