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 skills/repoprompt/repoprompt-ce/rpce-issue-creatornpx skills add repoprompt/repoprompt-ce --skill rpce-issue-creatorgit clone --depth 1 https://github.com/repoprompt/repoprompt-ceWrote 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/repoprompt/repoprompt-ce/rpce-issue-creator)<a href="https://agentmods.dev/skills/repoprompt/repoprompt-ce/rpce-issue-creator"><img src="https://agentmods.dev/badge/skills/repoprompt/repoprompt-ce/rpce-issue-creator.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.1 | $0.00059 | $0.01080 |
| Opus 5 | $0.00030 | $0.00540 |
| Sonnet 5 | $0.00012 | $0.00216 |
| Haiku 4.5 | $0.00006 | $0.00108 |
Grade A, and why
rpce-issue-creator 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 6d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RepoPrompt CE Issue Creator
Create concise, actionable issues for repoprompt/repoprompt-ce. Remove private or identifying data from source material before using it in a draft. Ask only for missing details that materially affect reproduction, routing, or acceptance.
Workflow
- Classify the request as a bug, regression, enhancement, task, docs issue, investigation follow-up, or question.
- Search open and closed issues in
repoprompt/repoprompt-cebefore drafting. Link likely duplicates; if the report is distinct, state the differing symptom, environment, version, or commit. Do not file blindly. - Draft the issue using the content and CE-specific evidence guidance below.
- Review the complete draft and remove or redact all private and identifying data.
- Show the user the exact final title, body, and proposed labels. Obtain immediate explicit approval to file; approval to investigate or draft is not approval to create the issue.
- Only after approval, run
gh issue create --repo repoprompt/repoprompt-cewith the reviewed payload. Report the URL. Note that issues from unapproved contributors may be auto-closed for maintainer review underCONTRIBUTING.md.
Write Actionable Content
- Use a specific title naming the affected area and observable problem or desired behavior.
- Open with impact and scope, then state expected versus actual behavior.
- Give the smallest deterministic reproduction: starting state, numbered actions or command, frequency, and result.
- Record only relevant environment facts: release or debug app, app version/build or commit, macOS version, architecture, and provider/runtime when material. Do not include environment dumps.
- Include a known-good version, first-bad version, or regression range when available.
- Summarize focused validation and evidence; distinguish confirmed facts from hypotheses.
- Keep scope, non-goals, dependencies, risks, and open questions only when they help maintainers act.
- Write acceptance criteria as observable outcomes, not implementation instructions; include regression coverage when appropriate.
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.
- 6d ago First seen · 58 lines · 59 tokens per session scan A b6d25ccc7acc
rpce-issue-creator is a skill published in the GitHub repository repoprompt/repoprompt-ce (900 stars, last pushed yesterday), licensed Apache-2.0. It adds 59 tokens to every session and 1,080 once invoked, about $0.0003 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-30.
Other skills, from other repositories
frame-macos-notification
Realistic macOS notification banner with app icon, title, and body, suited to video overlays or product teasers.
bcc-plan-spar
BCC align+lock+review PLAN.md for one slice (no product code). Slash: /bcc-plan-spar · chat: bcc:plan-spar · "lock PLAN" · spar the plan. Args: rounds=N (auto-review cap), review=self|subagent|cli|auto|off. Grill until clear enough (no default Q&A quota). Hand off to bcc-clean-cut after human APPROVE.
bcc-throughline
BCC global progress cockpit (plans.md/progress.md/findings.md). Slash: /bcc-throughline · chat: bcc:throughline · "where are we" · reprioritize · resume after /clear. Not for coding or full PLAN grill.
bcc-breaking-coding-chaos
BCC main skill: dual-loop coding workflow (throughline → plan-spar → clean-cut) or quick status+next. Slash: /bcc-breaking-coding-chaos · chat: bcc:breaking-coding-chaos · "run BCC" · "BCC status" · "what next BCC". Needs a real idea (1:1 implement). Args: goal text, or status. May pass plan-spar review budget as…
bcc-clean-cut
BCC minimal implement from locked PLAN.md (ponytail ladder + verify). Slash: /bcc-clean-cut · chat: bcc:clean-cut · "implement PLAN" after human APPROVE. Not for plan grill (use bcc-plan-spar).
x-harness-admission
Teach the x-harness admission workflow and completion-card discipline.