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 tomzx/agents --skill create-issuegit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/create-issue)<a href="https://agentmods.dev/skills/tomzx/agents/create-issue"><img src="https://agentmods.dev/badge/skills/tomzx/agents/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/tomzx/agents/create-issue"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-issue.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.00026 | $0.03154 |
| Opus 5.5 | $0.00010 | $0.01262 |
| Sonnet 5.5 | $0.00005 | $0.00631 |
| Haiku 4.5 | $0.00003 | $0.00315 |
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 22d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create GitHub Issue
Creates a structured GitHub issue in the specified repository with background, prioritized acceptance criteria (Must/Should), and (for private repositories) a justified time budget so implementers have clear scope and exit criteria.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - If no argument is provided, operate on
$REPO. ghCLI authenticated with write access to the target repositoryghxCLI available for posting the follow-up comment- Repository name in
owner/repoformat ($1), or omitted to use the repository in the current working directory - The
search-existing-issuesskill available for the duplicate search in step 1
Skill attribution (GitHub)
Before creating an issue with gh issue create, read github-post-attribution/SKILL.md and append the Created with footer for SKILL_DIR = create-issue to the issue body.
Communication guidelines (outbound text)
Before composing any text posted or drafted on the user's behalf, apply communication-guidelines/SKILL.md.
When this skill is invoked as part of an sdlc pipeline run, also include the SDLC phase footer described in github-post-attribution/SKILL.md (prepend the SDLC phase: <phase> (<FEAT-id> #<issue>) line above the Created with line).
Formatting
- Do not use curly or typographic quotation marks in any text you write for the issue (title, body, sections, lists, or examples).
Use straight ASCII double quotes (
") and straight apostrophes (') only. - Write one sentence per line throughout the issue body. Lists and checklist items follow their own format, but any prose paragraph should have each sentence on its own line.
Acceptance Criteria
- Split into Must (the exit gate, the minimum bar for "done") and Should (deferrable without blocking the issue).
- Aim for the smallest set that proves the issue is resolved. If Must grows beyond roughly 5 items, the issue is probably too broad and should be split rather than padded with more criteria.
- Each criterion must be testable (a concrete test can be written for it) and specific about what, not how.
- Put the happy path in Must. Move edge cases, error handling, and polish to Should unless they are part of the core definition of done.
- Omit the Should subsection entirely when there are no deferrable items. Do not invent nice-to-haves just to fill it.
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.
- 22d ago Changed · +34 lines 1b568e3a7cb7
- 24d ago Changed 344ac85556eb
- 27d ago Changed · +1 lines faec76f489fa
- 28d ago Changed · +5 lines b6695d52de82
- 1mo ago Changed a0f50a730b11
- 2mo ago First seen · 180 lines · 26 tokens per session scan A 1630ec8de07c
create-issue is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 3,154 once invoked, about $0.0001 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.