Borrowing it
Nothing to install: this file belongs to albertomarturelo/sii. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/albertomarturelo/sii/main/.agents/skills/issue-start/SKILL.mdgit clone --depth 1 https://github.com/albertomarturelo/siiWrote 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/albertomarturelo/sii/issue-start)<a href="https://agentmods.dev/skills/albertomarturelo/sii/issue-start"><img src="https://agentmods.dev/badge/skills/albertomarturelo/sii/issue-start/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/albertomarturelo/sii/issue-start"><img src="https://agentmods.dev/badge/skills/albertomarturelo/sii/issue-start.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.00047 | $0.00565 |
| Opus 5.5 | $0.00019 | $0.00226 |
| Sonnet 5.5 | $0.00009 | $0.00113 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
issue-start 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 yesterday.
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.
What it actually says
The user passes an issue number. If they don't, ask which (or list open
issues via gh issue list --repo albertomarturelo/sii --state open).
-
Fetch the issue:
gh issue view <n> --repo albertomarturelo/sii -
Parse the 6 fixed sections:
Context,Target,ADRs to load,Acceptance criteria,Reproduction(fixes only),Estimated sessions. If any required section is missing, STOP and tell the user the issue is malformed — propose editing it before starting. Don't infer. -
For each ADR listed in
ADRs to load, read the file indocs/decisions/. These set the constraints the implementation must satisfy. -
Read the file in
Pattern to mirrorONCE for shape. Skim, don't study. -
Do NOT read the files listed in
Targetyet — they are where the work goes, not where context comes from. -
Create the branch:
git switch -c <type>/GH-<n>-<slug>where<type>matches the issue's type label and<slug>is a short kebab-case summary. -
Summarize for the user, exactly:
- Objective (one line, from
Context). - Acceptance checklist (verbatim — this is the DoD; copy to the PR description on submit).
- ADRs loaded and what each constrains.
- Target paths (the files you'll write to).
- Pattern to mirror.
- Branch created:
<type>/GH-<n>-<slug>.
- Objective (one line, from
-
Ask: "Ready to start?"
If Estimated sessions > 1, remind the user the issue should have been
decomposed and ask whether to split it now via /issue-new.
Token discipline: do NOT scan target files or neighboring modules at this step. The issue body + ADRs are the spec. Code reading happens when implementation starts, not during orientation.
What ships with it
1 file 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.
- yesterday First seen · 52 lines · 47 tokens per session scan A 349a72a3f6b2
issue-start is a skill published in the GitHub repository albertomarturelo/sii (16 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 565 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-10-24.
Other skills, from other repositories
vc:watzup
Use when you need a read-only handoff summary of current branch state, local/remote refs, worktrees, active Flowser plans, selected-plan hints, and suggested next checks.
github-issues
Manage GitHub issues, pull requests, CI runs, and repository operations via the gh CLI.
jira
Operate Jira Cloud via its REST v3 API — issues, projects, sprints, boards, comments, transitions, JQL search. Use when the user wants to triage, bulk-update, report on, or otherwise interact with Jira programmatically without the MCP server installed.
linear
Query and mutate Linear issues, projects, cycles, teams, workflow states, and comments via its GraphQL API. Use when the user wants to read or change Linear data programmatically — without the MCP server, and without hand-navigating the Linear UI.
github
Operate on GitHub via the REST API — repos, PRs, issues, code search, actions, releases. Use when the user wants scripted / cross-repo operations, doesn't have gh installed, or needs behavior the gh CLI doesn't expose cleanly.
github-issues
Create, triage, label, assign GitHub issues via gh or REST.