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 Linearl/reasonix_skill_repo --skill gh-issue-submitgit clone --depth 1 https://github.com/Linearl/reasonix_skill_repoWrote 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/linearl/reasonix_skill_repo/gh-issue-submit)<a href="https://agentmods.dev/skills/linearl/reasonix_skill_repo/gh-issue-submit"><img src="https://agentmods.dev/badge/skills/linearl/reasonix_skill_repo/gh-issue-submit/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/linearl/reasonix_skill_repo/gh-issue-submit"><img src="https://agentmods.dev/badge/skills/linearl/reasonix_skill_repo/gh-issue-submit.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.00071 | $0.06864 |
| Opus 5.5 | $0.00028 | $0.02746 |
| Sonnet 5.5 | $0.00014 | $0.01373 |
| Haiku 4.5 | $0.00007 | $0.00686 |
Grade B, and why
gh-issue-submit 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.
curl -s -H "Accept: application/json" -d "client_id=01ab8ac9400c4e429b23&scope=repo read:user user:email" https://github.com/login/device/code Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
code=$(curl -s -o /dev/null -w "%{http_code}" "$A/$f") The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · +147 lines · +22 tokens per session c761595d8f7b
- 1mo ago First seen · 182 lines · 49 tokens per session scan B c6708666151a
gh-issue-submit is a skill published in the GitHub repository Linearl/reasonix_skill_repo (3 stars, last pushed 16d ago), with no licence file. It adds 71 tokens to every session and 6,864 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
contrib-watch
Watch incoming feedback from outside engineers on your open-source repos: comments, reviews, issues, mentions. Use when you need to find who replied to your pull requests or issues, triage human versus bot responses, and answer within a day with evidence.
issue-match
Measure a target repository's queue and find a live open issue the contribution would close, before opening a pull request there. Reports how many PRs are open, how many of the last N closed ones were actually merged, and which issue to attach to, because a cold PR into a dead queue is a wasted artifact. Triggers…
pr-review-watcher
Monitors for incoming PR reviews and summarizes their content. Determines approval/change-request/comment verdicts and extracts action items. Triggers on "did the PR review come in?", "when will the review arrive", "PR waiting" utterances.
pr-reply
Answer reviewers on your own pull requests in other people's repos: find threads where the ball is on your side, tell humans from bots, do exactly what was asked and reply with evidence. Use at the start of any GitHub session or on a new-review alert. Triggers: /pr-reply, /prr, answer the reviewers, who is waiting on…
peer-onboard
A procedure for bringing an outside lead or peer into a shared working setup, including their contact space, records, previous conversations, and ongoing session.
retro-lost
Run a retrospective for an abandoned agent session (untouched for over 24 hours, never closed with a retro): rebuild context cold from the transcript, list what was built, sort Keep/Drop/Try and file the durable parts. Use from a nightly routine or on demand. Triggers: /retro-lost, retro for an abandoned session.