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/termio-sh/termio/issue-creatornpx skills add termio-sh/termio --skill issue-creatorgit clone --depth 1 https://github.com/termio-sh/termioWrote 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/termio-sh/termio/issue-creator)<a href="https://agentmods.dev/skills/termio-sh/termio/issue-creator"><img src="https://agentmods.dev/badge/skills/termio-sh/termio/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 | $0.00096 | $0.01441 |
| Opus 5 | $0.00048 | $0.00720 |
| Sonnet 5 | $0.00019 | $0.00288 |
| Haiku 4.5 | $0.00010 | $0.00144 |
Grade A, and why
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 4d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vague user request → actionable GitHub issue
Preserve the user's voice, identify the underlying problem, add only grounded repository context, and create the smallest honest issue that moves the work forward. Never turn missing information into confident requirements.
Workflow
1. Normalize the raw input
Handle all three input modes:
- Pasted text: preserve the most useful original sentence verbatim.
- Screenshot: inspect both visible text and UI context. Transcribe only what
is legible and mark uncertainty. Keep the original image for
Evidence. - Mixed: treat the pasted explanation as context and the screenshot as primary evidence unless they conflict; surface any conflict.
Build a private scratch intake before drafting:
| Field | Extract |
|---|---|
| Actor | Who experiences this? |
| Situation | When and where does it happen? |
| Friction | What is hard, broken, or missing now? |
| Desired outcome | What should the user be able to achieve? |
| Impact | Why does it matter? |
| Explicit constraints | What did the user actually require? |
| Unknowns | What remains unclear? |
Do not force the request into “As a user, I want…” language. Preserve a direct quote when it expresses the pain better than a summary.
If the message is phrased as a question, identify the latent need but first check whether existing behavior or documentation already answers it. Do not file a feature request for something the product already supports.
2. Resolve repository conventions
Use an explicitly named repository; otherwise resolve the current checkout:
gh auth status
gh repo view --json nameWithOwner,defaultBranchRef,visibility,hasIssuesEnabled
gh issue list --state all --limit 10 --json number,title,state,url
rg --files -g 'CONTRIBUTING*' -g '.github/ISSUE_TEMPLATE/**'
Read any relevant issue template or contributing guide. Match the repository's language, headings, title style, and metadata conventions. Do not invent labels, types, milestones, or assignees.
What ships with it
2 files 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.
- 4d ago First seen · 174 lines · 96 tokens per session scan A 1db2128064de
issue-creator is a skill published in the GitHub repository termio-sh/termio (359 stars, last pushed 4d ago), licensed MIT. It adds 96 tokens to every session and 1,441 once invoked, about $0.0005 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
workflows
Execute a workflow script that orchestrates multiple subagents deterministically. Use when the user explicitly requests a workflow, multi-agent orchestration, parallel or sequential agent pipelines, structured agent outputs, or a durable background workflow run.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
deck-pitch
10 页融资 deck, 白底 + 蓝紫渐变 hero, traction 柱状, $X.XM ask.
argent-tv-interact
Control and inspect TV apps via argent — Apple TV (tvOS), Android TV (leanback), and Amazon Fire TV (Vega). Boot the target, read focus, navigate with the D-pad remote, type, screenshot, and on Vega debug the JS runtime (evaluate, console logs, network inspector). Use when a task targets a TV (runtimeKind "tv", or…
review-offered-task
Review a task that has been offered to you and decide whether to accept or reject it.
aidd-dev:08:for-sure
Iterative agent loop that tracks attempts and retries until a success condition is met. Use when the user says "for sure", "make sure", "keep trying until", "loop until done", "don't stop until", or needs guaranteed completion of a task with explicit success criteria.