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/.claude/commands/issue-new.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/commands/albertomarturelo/sii/issue-new)<a href="https://agentmods.dev/commands/albertomarturelo/sii/issue-new"><img src="https://agentmods.dev/badge/commands/albertomarturelo/sii/issue-new.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.1 | $0.00000 | $0.00809 |
| Opus 5 | $0.00000 | $0.00404 |
| Sonnet 5 | $0.00000 | $0.00162 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
issue-new 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
Guide the user through creating a new GitHub issue on albertomarturelo/sii
using the fixed 6-section body template.
Ask, in order, and confirm each answer before moving on:
- Type.
feature|fix|chore|docs|spike - Title. Imperative mood, ≤80 chars, English. e.g. "Add rut parser + Mod-11 DV to @albertomarturelo/sii-core".
- Context. 2–4 sentences: what is the trigger, what is the user-visible outcome.
- Target location. Concrete paths. For net-new, name the package +
file (e.g.
packages/core/src/rut.ts — new file). - Reference pattern. An existing file/module to mirror in shape, naming, and conventions. Skip ONLY if no analog exists; flag it.
- ADRs to load. ADR numbers the agent must read before starting.
At minimum the architectural ones the change touches:
ADR-003for anything crossing the core boundary / ports,ADR-004for any SII domain code,ADR-005for identity/operate,ADR-006for auth. If a needed decision isn't an ADR yet, STOP and run/decision:newfirst. - Acceptance criteria (DoD). Bulleted markdown
[ ]items. Include all three of:- Behavior — what works at the end (concrete CLI/MCP/plugin output
or
@albertomarturelo/sii-coreAPI). - Tests — what tests exist (
<module>.test.ts, vitest); state explicitly that fixtures are synthetic (no real PII). - Documentation — which of
CONVENTIONS.md,STACK.md,ARCHITECTURE.md,ROADMAP.md, asii-contract/*.md, or a new ADR is updated.
- Behavior — what works at the end (concrete CLI/MCP/plugin output
or
- Reproduction steps. ONLY for
fix. Minimal repro to confirm the bug (state whether the session was cached or fresh for SII bugs). - Estimated sessions.
1|2–3|4+. If > 1, propose decomposition into sub-issues before continuing. - Labels. Type label + scope labels (
core,cli,mcp,auth,portal,identity,docs,tests).
Then generate the body using the fixed template (do NOT deviate from
section order or names — /issue:start parses by section header):
## Context
<step 3>
## Target
- Files / dirs: <step 4>
- Pattern to mirror: <step 5>
## ADRs to load
- ADR-NNN
## Acceptance criteria
- [ ] <step 7>
## Reproduction (fixes only)
<step 8 — OR omit this section entirely if not a fix>
## Estimated sessions
<step 9>
Then run:
gh issue create --repo albertomarturelo/sii \
--title "<step 2>" --body "<body above>" \
--label "<step 1>,<step 10 scopes>"
Output the issue URL when done. English only.
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 Changed 5402c1758c6c
- 6d ago First seen · 76 lines · 0 tokens per session scan A fb965fb0d886
issue-new is a command published in the GitHub repository albertomarturelo/sii (5 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 809 tokens. 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 commands, from other repositories
report-issue-with-atomic
Open an issue against the atomic-claude repo itself (bugs/feature requests with the installed config, not the user's current project).
report-issue
Open a atomic GitHub issue via gh. Bug report or feature request — auto-detect from user's description.
roadmap-track.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
vision-adjust.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
vision-init.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
create-github-epic.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.