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 runxhq/runx --skill issue-intakegit clone --depth 1 https://github.com/runxhq/runxWrote 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/runxhq/runx/issue-intake)<a href="https://agentmods.dev/skills/runxhq/runx/issue-intake"><img src="https://agentmods.dev/badge/skills/runxhq/runx/issue-intake/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/runxhq/runx/issue-intake"><img src="https://agentmods.dev/badge/skills/runxhq/runx/issue-intake.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00022 | $0.01945 |
| Opus 5 | $0.00011 | $0.00972 |
| Sonnet 5 | $0.00004 | $0.00389 |
| Haiku 4.5 | $0.00002 | $0.00194 |
Grade A, and why
issue-intake 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 5d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Intake
Convert an inbound thread, support report, or operator request into one explicit intake decision plus the parent change artifact that downstream planning or mutation lanes must share.
This skill does not mutate code, open tickets, or publish replies directly. Its
job is to classify the report, summarize it, draft the next helpful response,
and recommend the next governed lane. That next lane must be explicit:
issue-to-pr, work-plan, reply-only, or manual-review.
In supervisor-style flows, issue-intake is also the commencement gate. It
decides whether work may start at all, whether the next step should stop at a
review comment first, and whether mutation is justified yet. A recommended lane
is not the same thing as build permission.
Use issue-to-pr only when the requested change is bounded enough for one
governed remediation lane. Use work-plan for larger or multi-step
work. Use reply-only when the right answer is guidance rather than mutation.
Use manual-review when the report is ambiguous, risky, or missing key context.
Ground category, severity, and routing in the visible request and supplied
product constraints. Put uncertainty in operator_notes instead of inventing
confidence. The suggested reply should sound like the project owner and lead
with the decision or next action, not read like a ticket macro.
Output Contract
intake_report must contain:
category: one ofbug,feature_request,docs,billing,account,question, orotherseverity: one oflow,medium,high, orcriticalsummary: concise summary of the actual request or reportsuggested_reply: a user-facing reply draft or operator handoff noterecommended_lane:issue-to-pr,work-plan,reply-only, ormanual-reviewrationale: why that lane is the right next stepneeds_human: booleanoperator_notes: array of caveats, missing context, or escalation notes
intake_report may also include supervisor-facing control fields:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 189 lines · 22 tokens per session scan A cee1320a8a8e
issue-intake is a skill published in the GitHub repository runxhq/runx (84 stars, last pushed today), licensed Apache-2.0. It adds 22 tokens to every session and 1,945 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-09-03.
Other skills, from other repositories
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-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.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
dd-synthesis
Synthesize findings from multiple specialist agents into a coherent investment recommendation. Use when combining reports from 9+ specialist agents into a single decision document.
dd-report-format
Standard output format for due diligence analysis reports. Use when producing your final analysis to ensure consistency across all specialist agents.
dd-risk-scoring
Calculate weighted risk scores from specialist agent reports. Use when synthesizing multiple due diligence reports into an overall investment risk assessment.