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/issues-setup)<a href="https://agentmods.dev/commands/artemiopadilla/agent-triforce/issues-setup"><img src="https://agentmods.dev/badge/commands/artemiopadilla/agent-triforce/issues-setup/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/issues-setup"><img src="https://agentmods.dev/badge/commands/artemiopadilla/agent-triforce/issues-setup.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.00017 | $0.00627 |
| Opus 5 | $0.00009 | $0.00313 |
| Sonnet 5 | $0.00003 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
issues-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.
What it actually says
Configure issue tracker MCP integration for the Agent Triforce system. Issue trackers connect agents to your project management workflow:
- Prometeo pulls ticket details into spec creation
- Forja updates ticket status during implementation
- Centinela links review findings to open issues and can create new issues for critical findings
Supported Issue Trackers
| Tracker | Template | Key Features |
|---|---|---|
| Linear | templates/mcp/linear.mcp.json |
Pull ticket details, update status, create issues |
| Jira | templates/mcp/jira.mcp.json |
Pull ticket details, update status, create issues |
| GitHub Issues | templates/mcp/github-issues.mcp.json |
Link issues to commits, update status, create issues |
Setup Steps
-
Choose which issue tracker(s) to configure. Multiple trackers can be configured simultaneously.
-
Copy the selected template(s) to
.mcp.jsonin the project root. If.mcp.jsonalready exists, merge the newmcpServersentries. -
Set the required environment variables for each tracker:
Linear:
export LINEAR_API_KEY="lin_api_..." export LINEAR_TEAM_ID="your-team-id"Get your API key: Linear Settings > API > Personal API keys
Jira:
export JIRA_URL="https://yourteam.atlassian.net" export JIRA_EMAIL="[email protected]" export JIRA_API_TOKEN="your-api-token" export JIRA_PROJECT_KEY="PROJ"Get your API token: https://id.atlassian.com/manage-profile/security/api-tokens
GitHub Issues:
export GITHUB_TOKEN="ghp_..." export GITHUB_OWNER="your-org-or-user" export GITHUB_REPO="your-repo"Create a token: https://github.com/settings/tokens (needs
reposcope) -
Verify the connection by asking the agent to list recent issues.
How Agents Use Issue Trackers
| Agent | Read | Write | When |
|---|---|---|---|
| Prometeo | Pull ticket details into specs | -- | During /agent-triforce:feature-spec |
| Forja | Read linked issues | Update status, add implementation comments | During SIGN OUT |
| Centinela | Read linked issues | Create issues for Critical/High findings (opt-in) | During review |
Business Rules
- Each tracker is configured independently -- all three can be active simultaneously
- Read-write for status updates and issue creation; read-only for ticket content
- Issue creation from Centinela findings is opt-in per run (default: off)
- If no issue tracker is configured, agents proceed normally with no error
Templates location: templates/mcp/
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 · 68 lines · 17 tokens per session scan A fa31e68a079f
issues-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 627 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
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.
OPSX: Fast Forward
Create a change and generate all artifacts needed for implementation in one go.
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: Bulk Archive
Archive multiple completed changes at once.