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 skills add intentic/intentic --skill redminegit clone --depth 1 https://github.com/intentic/intenticWrote 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/skills/intentic/intentic/redmine)<a href="https://agentmods.dev/skills/intentic/intentic/redmine"><img src="https://agentmods.dev/badge/skills/intentic/intentic/redmine/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/skills/intentic/intentic/redmine"><img src="https://agentmods.dev/badge/skills/intentic/intentic/redmine.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.00034 | $0.00437 |
| Opus 5.5 | $0.00014 | $0.00175 |
| Sonnet 5.5 | $0.00007 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade B, and why
redmine scanned grade B with 2 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 1mo 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
- Create an issue: `curl -s -X POST -H "X-Redmine-API-Key: $REDMINE_API_KEY" -H "Content-Type: application/json" -d '{"issue":{"project_id":<PID>,"subject":"...","description":"..."}}' "$REDMINE_URL/issues.json"` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Instance in `$REDMINE_URL`, API key in `$REDMINE_API_KEY`. Talk to `$REDMINE_URL` with `curl`. What it actually says
Redmine (connected)
Instance in $REDMINE_URL, API key in $REDMINE_API_KEY. Talk to $REDMINE_URL with curl.
Header: -H "X-Redmine-API-Key: $REDMINE_API_KEY".
- Who am I:
curl -s -H "X-Redmine-API-Key: $REDMINE_API_KEY" "$REDMINE_URL/users/current.json" | jq '.user | {id, login}' - Projects:
curl -s -H "X-Redmine-API-Key: $REDMINE_API_KEY" "$REDMINE_URL/projects.json" | jq '.projects[] | {id, identifier, name}' - Open issues:
curl -s -H "X-Redmine-API-Key: $REDMINE_API_KEY" "$REDMINE_URL/issues.json?status_id=open&limit=50" | jq '.issues[] | {id, subject, status: .status.name}' - One issue:
curl -s -H "X-Redmine-API-Key: $REDMINE_API_KEY" "$REDMINE_URL/issues/<ID>.json" | jq '.issue | {id, subject, description}' - Create an issue:
curl -s -X POST -H "X-Redmine-API-Key: $REDMINE_API_KEY" -H "Content-Type: application/json" -d '{"issue":{"project_id":<PID>,"subject":"...","description":"..."}}' "$REDMINE_URL/issues.json" - Update an issue:
curl -s -X PUT -H "X-Redmine-API-Key: $REDMINE_API_KEY" -H "Content-Type: application/json" -d '{"issue":{"notes":"...","status_id":<SID>}}' "$REDMINE_URL/issues/<ID>.json"
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.
- 1mo ago First seen · 17 lines · 34 tokens per session scan B a61b076ad922
redmine is a skill published in the GitHub repository intentic/intentic (85 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 437 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-06.
Other skills, from other repositories
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
linear
Manage Linear issues, projects, and teams via the GraphQL API. Create, update, search, and organize issues. Uses API key auth (no OAuth needed). All operations via curl — no dependencies.
notion
Notion API for creating and managing pages, databases, and blocks via curl. Search, create, update, and query Notion workspaces directly from the terminal.