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 specsnl/agent-specs --skill implement-issuegit clone --depth 1 https://github.com/specsnl/agent-specsWrote 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/specsnl/agent-specs/implement-issue)<a href="https://agentmods.dev/skills/specsnl/agent-specs/implement-issue"><img src="https://agentmods.dev/badge/skills/specsnl/agent-specs/implement-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/specsnl/agent-specs/implement-issue"><img src="https://agentmods.dev/badge/skills/specsnl/agent-specs/implement-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.00117 | $0.00711 |
| Opus 5.5 | $0.00047 | $0.00284 |
| Sonnet 5.5 | $0.00023 | $0.00142 |
| Haiku 4.5 | $0.00012 | $0.00071 |
Grade A, and why
implement-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 1mo 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement an issue
Turn an issue (GitHub or Linear) into a branch of clean, incremental commits — without opening a pull request. The user opens the PR when they decide it's ready; this skill deliberately stops just short of that.
Phase 1 — Read the issue
Fetch the full issue before touching git so you understand the actual requirement.
- GitHub — prefer a GitHub MCP tool (e.g.
get_issue) when one is available; otherwise use the CLI:gh issue view <number> --json title,body,labels,comments. - Linear — use the Linear MCP
get_issue(accepts the issue identifier such asABC-456).
Extract and note:
- The concrete requirement and scope.
- Acceptance criteria / definition of done.
- Any linked issues, designs, or discussion in comments that change the approach.
If the requirement is ambiguous, ask the user before implementing.
Phase 2 — Create a branch
Never implement directly on the base branch.
-
Confirm the working tree is clean (
git status) and note the current base branch (usuallymain). -
Create and switch to a new branch with a descriptive name derived from the issue id and a short slug of its title:
feat/<issue-id>-<slug>for new functionalityfix/<issue-id>-<slug>for bug fixeschore/<issue-id>-<slug>/docs/.../refactor/...as appropriate
git switch -c feat/GH-123-short-slug
Phase 3 — Implement
Implement the change following the repository's existing conventions and patterns. Match the surrounding code style; reuse existing utilities rather than adding new ones. Run the project's checks/tests as you go.
Phase 4 — Commit nicely
Commit as you complete logical units of work — not one large dump at the end.
- Small, self-contained commits, each leaving the tree in a working state.
- Clear, imperative subject lines that follow the repo's convention (e.g.
Conventional Commits when the repo uses them), referencing the issue where it
helps (e.g.
feat: add X (GH-123)orRefs ABC-456). - Keep unrelated changes out of a commit.
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.
- 1mo ago Changed · +1 lines 47e9db292871
- 1mo ago First seen · 84 lines · 117 tokens per session scan A 02077d6039a7
implement-issue is a skill published in the GitHub repository specsnl/agent-specs (2 stars, last pushed 1mo ago), licensed MIT. It adds 117 tokens to every session and 711 once invoked, about $0.0005 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.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…