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 cboone/agent-harness-plugins --skill create-issuegit clone --depth 1 https://github.com/cboone/agent-harness-pluginsWrote 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/cboone/agent-harness-plugins/create-issue)<a href="https://agentmods.dev/skills/cboone/agent-harness-plugins/create-issue"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-plugins/create-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/cboone/agent-harness-plugins/create-issue"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-plugins/create-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.00054 | $0.01270 |
| Opus 5.5 | $0.00022 | $0.00508 |
| Sonnet 5.5 | $0.00011 | $0.00254 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
create-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 15d 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.
Create Issue
Create GitHub issues cleanly by writing the body to a tmpfile and passing it via --body-file.
Why This Skill Exists
When creating GitHub issues, passing a large multiline --body string directly to gh issue create in a Bash command triggers Claude Code permission prompts because the command appears complex. This skill avoids that by using the Write tool to create a temporary file containing the issue body, then passing a short, simple gh issue create --body-file command to Bash.
Workflow
1. Gather Issue Details
Determine the issue title, body, labels, and assignees from the user's request. If the user's request is vague, ask clarifying questions. At minimum, you need:
- Title: A concise summary of the issue
- Body: A detailed description (can be multiple paragraphs, include code blocks, checklists, etc.)
Optional fields:
- Labels: Relevant labels (e.g.,
bug,enhancement,documentation) - Assignees: GitHub usernames to assign
- Milestone: A milestone to associate with the issue
- Project: A GitHub project to add the issue to
2. Confirm the Repository
If the user specifies a repository (e.g., "file an issue on org/repo"), use the --repo flag. Otherwise, the issue will be created in the current repository.
3. Write the Issue Body to a Tmpfile
Follow the tmpfile procedure for non-secret GitHub bodies. Resolve its path relative to this SKILL.md file's directory. Create a unique path and write the full issue body there. Wait for the write to finish before calling gh. TMPFILE below means that exact path.
4. Create the Issue
Run a single, short gh issue create command using the tmpfile path from step 3:
gh issue create --title "Issue title here" --body-file TMPFILE
Add optional flags as needed:
gh issue create --title "Issue title here" --body-file TMPFILE --label "bug" --label "enhancement" --assignee "@me"
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.
- 15d ago Changed · -11 lines a18c84ee17d1
- 20d ago Changed · +1 lines · +15 tokens per session 8007f5d2ff1a
- 29d ago Changed · -4 tokens per session 669667b33481
- 1mo ago Changed 0ba918cf0a59
- 1mo ago Changed · -4 lines · -48 tokens per session 7cbccd3a1ee8
- 1mo ago Changed · +22 lines b681a7b3dfac
- 1mo ago First seen · 93 lines · 91 tokens per session scan A 96d82cad3614
create-issue is a skill published in the GitHub repository cboone/agent-harness-plugins (2 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 1,270 once invoked, about $0.0002 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
linear-app-setup
Create and configure a Linear agent app so the assistant can manage issues, projects, and workflows under its own identity.
factory-mcp
Use the Warp Factory MCP to hand work to a software factory and collaborate with it — bundle local work and send it to the cloud, find factory tasks from a Slack thread / Linear ticket / description, and pull a task down to test or iterate locally and hand it back.
oz-finish-task
Report task completion or failure back to the Oz platform when done with a task.
oz-notify-user
Send a progress notification to the user who triggered this Oz task (e.g., via Slack or Linear).
todoist-cli
Manage Todoist tasks, projects, labels, filters, sections, comments, reminders, and workspaces via the td CLI. Use when the user wants to view, create, update, complete, or organize Todoist items, or mentions tasks, inbox, today, upcoming, projects, labels, or filters.
model-triage
Adopt the per-issue model-selection convention in a repo — tier every open issue, apply the model: labels, board field, and callouts behind an approval gate. Also runs in maintenance mode to sweep up unlabeled issues and label/field drift.