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.
npx agentmods add agents/illodev/taiga-mcp/taiga-issuesgit clone --depth 1 https://github.com/illodev/taiga-mcpWrote 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/agents/illodev/taiga-mcp/taiga-issues)<a href="https://agentmods.dev/agents/illodev/taiga-mcp/taiga-issues"><img src="https://agentmods.dev/badge/agents/illodev/taiga-mcp/taiga-issues.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 | $0.00045 | $0.01121 |
| Opus 5 | $0.00023 | $0.00561 |
| Sonnet 5 | $0.00009 | $0.00224 |
| Haiku 4.5 | $0.00005 | $0.00112 |
Grade A, and why
Taiga Issues 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 112 lines · 45 tokens per session scan A 299944d0b736
Taiga Issues is an agent published in the GitHub repository illodev/taiga-mcp (2 stars, last pushed 5mo ago), with no licence file. It adds 45 tokens to every session and 1,121 once invoked, about $0.0002 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 agents, from other repositories
product-owner
Analyzes the codebase, issues, and TODOs to propose prioritized work items. Run when deciding what to work on next or reviewing the project backlog.
Technical Manager
Engineering manager that coordinates all agents, tracks progress, prioritizes work, and surfaces decisions to the human operator.
dependabot-pr-merger
Use this agent when the user wants to review, validate, and merge open Dependabot pull requests in the claworc repository (https://github.com/gluk-w/claworc). This agent handles bulk processing of dependency update PRs, ensuring CI checks pass before merging. Context: User wants to clean up the backlog of Dependabot…
issue-tracker
Issues and PRDs for this repo live as Markdown files in .scratch/.
triage-labels
Use only the statuses a workflow needs; Room threads currently use needs-triage for the PRD and ready-for-agent for implementation slices.
claudette-pm
Claudette PM Agent v1.2.0 (Project Manager & Requirements Analyst).