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 rsenna/rs-agent-plugin --skill fix-mapped-issuegit clone --depth 1 https://github.com/rsenna/rs-agent-pluginWrote 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/rsenna/rs-agent-plugin/fix-mapped-issue)<a href="https://agentmods.dev/skills/rsenna/rs-agent-plugin/fix-mapped-issue"><img src="https://agentmods.dev/badge/skills/rsenna/rs-agent-plugin/fix-mapped-issue/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/rsenna/rs-agent-plugin/fix-mapped-issue"><img src="https://agentmods.dev/badge/skills/rsenna/rs-agent-plugin/fix-mapped-issue.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.00073 | $0.01348 |
| Opus 5.5 | $0.00029 | $0.00539 |
| Sonnet 5.5 | $0.00015 | $0.00270 |
| Haiku 4.5 | $0.00007 | $0.00135 |
Grade A, and why
fix-mapped-issue 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 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.
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Mapped Issue
Steps 4–6 of the issue lifecycle: implement the mapped tasks, ship them via the
pull-request process, then update and close the issue. Assumes
map-issue-to-tasks already produced tasks/issue-<n>-<slug>.md. If that file
doesn't exist, run map-issue-to-tasks first.
Reuses the sibling skills' scripts (this plugin's other skills, installed as
siblings of this one under the same skills root — resolve these relative to
wherever this fix-mapped-issue skill itself was loaded from):
../pull-request-process/pr.sh(branch/push/PR/threads)../map-issue-to-tasks/issue.sh(closefor the final comment)
Portability — read the project's specifics first
From the project's AGENTS.md: the base branch and the
quality gate command + coverage bar (e.g. what-about:
mix precommit --cover, ≥ 90% — see AGENTS.md:23–30). Pass the base branch as
BASE= to pr.sh.
Do this (per task, until the issue is done)
- Pick the next task from
tasks/issue-<n>-*.md: the next unchecked box, respecting dependency order. If the file predates the checkbox convention (any heading with no leading- [ ]/- [x]), retrofit a checkbox onto every heading before picking —- [x]for tasks the file already notes as done/merged,- [ ]for the rest — so the "next unchecked box" rule has something to operate on. If it's a 🔒 ask-first gate (new dependency, DB migration, CI/secret change), pause and get explicit approval before starting. - Implement via the
incremental-implementationandtest-driven-developmentskills. New or changed behaviour must be described by tests (behaviour-asserting, not coverage-padding). - Ship it via the
pull-request-processskill — one task ≈ one PR:pr.sh start(thencdinto the worktree path it prints) → implement/commit → run the gate → runpull-request-processstep 3's exactrequesting-code-reviewpass and fix what it flags → re-run the gate if any code changed →REVIEWED=1 pr.sh push→pr.sh open→ STOP (never merge). Then handle review threads per that skill. - After the maintainer/bots merge, tick the task's checkbox in
tasks/issue-<n>-*.md(- [ ]→- [x]) and append the merged PR link to that task's heading line in exactly this form:— ✅ merged (#<n>)— a fixed syntax so later automation can parse it reliably. If a task shipped across more than one PR, list every merged PR in that same parenthetical, in merge order, comma-separated (— ✅ merged (#9, #12)); never drop an earlier PR link when a later one for the same task lands. This edit is itself a change to a tracked file, so commit and ship it through the samepull-request-processflow as any other change — never push it straight to the base branch. Either give it its own small PR or fold it into the next task's branch if you're about to start that task anyway. Then move to the next task. Repeat until every task is merged.
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 Changed · +18 lines 12715c8b0995
- 1mo ago First seen · 83 lines · 73 tokens per session scan A 90c08af1d74a
fix-mapped-issue is a skill published in the GitHub repository rsenna/rs-agent-plugin (2 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 1,348 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…