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 onsager-ai/dev-skills --skill issue-specgit clone --depth 1 https://github.com/onsager-ai/dev-skillsWrote 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/onsager-ai/dev-skills/issue-spec)<a href="https://agentmods.dev/skills/onsager-ai/dev-skills/issue-spec"><img src="https://agentmods.dev/badge/skills/onsager-ai/dev-skills/issue-spec/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/onsager-ai/dev-skills/issue-spec"><img src="https://agentmods.dev/badge/skills/onsager-ai/dev-skills/issue-spec.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.00037 | $0.00797 |
| Opus 5.5 | $0.00015 | $0.00319 |
| Sonnet 5.5 | $0.00007 | $0.00159 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
issue-spec 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 18d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue specification
Scope
This skill owns specification method, not which changes require a spec. Read AGENTS.md and the relevant repo workflow overlay for the target repository, always-spec surfaces, labels, required sections and exceptions. An explicit request to write a spec is sufficient to start; do not re-ask whether to do it. Use the repository's declared spec medium. Use GitHub issues when it adopts the issue-based SDD loop; do not migrate another repository's spec format by inference.
Prerequisites
Know the intended change, target repo and applicable contract. For GitHub work, use harness-operations only if capability mapping is needed. No personal installation or particular GitHub tool is required. Read the format reference when drafting and use the template as a starting point, not extra policy.
Procedure
- Discover relevant code, recent changes and existing issues/specs. Reuse or amend related work instead of creating a duplicate. Resolve the target repo from its checkout/remote and contract; do not infer it from the skill's source repo.
- Capture intent with Overview, Design, independently verifiable Plan items, matching Test items, Alignment and optional Notes. Include the repo's required impact/example sections. Keep the spec near 2000 tokens or less; split a larger feature into a parent and independently scoped children.
- State boundaries in Alignment. Proceed with already authorized implementation decisions. For a concrete unresolved human boundary needed for the work, use the structured question capability mapped by harness-operations; name its source, affected Plan items, options and tradeoffs. A plain-text question or Human decides checklist alone does not request the decision. Wait for an explicit answer before dependent work; continue independent authorized work. Reconcile the answer into the spec in the same sitting and clear answered blockers. If no permitted question tool exists, state that limitation and use the established handoff channel without assuming an answer.
- Validate scope, invariants, test coverage, dependencies and required labels. In GitHub bodies keep each prose paragraph or list item on one source line; blank lines separate blocks. Do not mark Plan items complete before delivery.
- Publish or update the spec through an available authorized tool. Apply existing repo labels, priority and area conventions; do not create a new taxonomy merely because this procedure uses one in an example. Establish child relationships with native sub-issues where supported, otherwise record explicit links.
- Hand ready work to pre-push and pr-lifecycle. Use the repository's worktree/branch rules. The common procedure does not choose a harness branch prefix.
What ships with it
4 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.
- 18d ago Changed · -234 lines · -155 tokens per session 08cf37607416
- 1mo ago First seen · 301 lines · 192 tokens per session scan A 8e83a72aaad1
issue-spec is a skill published in the GitHub repository onsager-ai/dev-skills (7 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 797 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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
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,"…