Borrowing it
Nothing to install: this file belongs to ianphil/chamber. 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/ianphil/chamber/master/.github/skills/issue-slate/SKILL.mdgit clone --depth 1 https://github.com/ianphil/chamberWrote 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/ianphil/chamber/issue-slate)<a href="https://agentmods.dev/skills/ianphil/chamber/issue-slate"><img src="https://agentmods.dev/badge/skills/ianphil/chamber/issue-slate/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/ianphil/chamber/issue-slate"><img src="https://agentmods.dev/badge/skills/ianphil/chamber/issue-slate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 300 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00076 | $0.03182 |
| Opus 5.5 | $0.00030 | $0.01273 |
| Sonnet 5.5 | $0.00015 | $0.00636 |
| Haiku 4.5 | $0.00008 | $0.00318 |
Grade A, and why
issue-slate 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 2mo 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Slate Skill
Drive a labeled or explicitly supplied GitHub issue slate from triage through reviewable PRs.
This skill coordinates the Chamber ship skill. Use gh for all GitHub operations. Never use MCP. The default base branch is master, and the default repository is ianphil/chamber.
When to use
Use this skill when the user asks to:
- Work through all issues with a label such as
now,next, orlater. - Turn a set of GitHub issues into an execution plan.
- Create several PRs from an issue batch.
- Run the Chamber loop of plan -> do -> ship repeatedly.
- Generalize, replay, or continue a prior issue-slate workflow.
Do not use this skill for a single already-scoped PR. Use the ship skill directly for that.
Defaults
- User:
ianphil. - Repository:
ianphil/chamber. - Base branch:
master. - Labels are priority buckets:
now,next,later. - Default slate label: ask if unclear; otherwise use the label named by the user.
- Prefer Git Town stacks for slate execution. Independent PRs are the exception, not the default, when every PR needs release metadata.
- Use
ghfor issue and PR operations. - Never use MCP.
- Do not run
npm run make:sandbox. - If packaging/runtime smoke is needed, use
npm run packageinstead. - Run
npm run lintandnpm testfor each PR through theshipskill. - Use the narrowest existing runtime smoke that proves the changed surface still runs.
- Run Uncle Bob for non-trivial, runtime, architectural, or security-sensitive PRs, and fix critical findings.
- Include
Closes #NNNorFixes #NNNfor every issue intentionally addressed by a PR. - Let the
shipskill recommend the version bump, then accept the recommendation unless the user gives a reason to override. For a stack, apply sequential version bumps down the stack so child PRs do not duplicate parent release metadata. - Draft and apply a matching
CHANGELOG.mdentry for every non-trivial PR. - Do not merge PRs unless the user explicitly asks. Creating reviewable PRs is the default end state.
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.
- 2mo ago First seen · 340 lines · 76 tokens per session scan A 86bef376bdc7
issue-slate is a skill published in the GitHub repository ianphil/chamber (12 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 3,182 once invoked, about $0.0003 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-30.
Other skills, from other repositories
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
01-sdlc
Orchestrates a request from framing to a draft pull request, autonomous or supervised, isolating implementation, independent review, and final outcome challenge. Use when the user wants to deliver a change end to end. Not for one step.
02-backlog
Orchestrates a product backlog end to end. Use when the user wants to ask what it holds, or to run intake, triage, refinement, review, lifecycle events, ordering, health checks, or repair. Not for one known artifact step.
02-user-stories
Produces or refines ordered User Stories from an Epic, Product Brief, PRD, or bounded request. Use when the user wants to slice, write, assess, order, or persist Stories. Not for Epics or implementation.
07-epic
Produces or refines an outcome-based Epic for a product backlog. Use when the user wants to frame, review, resume, or persist an Epic. Not for Product Briefs, User Stories, or implementation.
08-three-amigos
Assesses an Epic or Story through one product, delivery, or quality lens, then reconciles three caller-supplied reports. Use when the user wants to refine one before a backlog change. Not for spawning or writing.