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.
git clone --depth 1 https://github.com/choi88andys/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/plugins/choi88andys/skills/immutable)<a href="https://agentmods.dev/plugins/choi88andys/skills/immutable"><img src="https://agentmods.dev/badge/plugins/choi88andys/skills/immutable/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/plugins/choi88andys/skills/immutable"><img src="https://agentmods.dev/badge/plugins/choi88andys/skills/immutable.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
immutable 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 5d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "immutable",
"version": "0.16.0",
"description": "Append-only SDD toolkit covering the full 7-step flow from problem framing through PR creation. Skills: /immutable:init (starter bootstrap), /immutable:office-hours (premise + alternatives), /immutable:prd (pitch authoring — WHAT), /immutable:design (app-side context), /immutable:plan-review-ceo (scope challenge + adversarial review), /immutable:plan-review-eng (engineering review + worktree analysis), /immutable:adr (Architecture Decision Records — WHY), /immutable:ship (PR creation), /immutable:migrate (one-shot config + profile schema migration). Authoring skills enforce a grill-me interview, multi-persona adversarial review, and a 90% completeness gate. Ships a PostToolUse read gate (the plugin's first hook) that withholds the body of a deprecated doc at Read time, so a dead spec cannot be mistaken for current requirements. The flow runs standalone — no external harness required. Built from two layered fusions: the immutable-prd lineage (append-only artifacts with supersede chains for accuracy + accountability) and the gstack lineage (transient → artifact flow pipeline). See plugin README's Design heritage for the full origin story. In a repo that opts in, /immutable:prd also authors against a tracker ticket's binding sections (the requirement contract): it records the ticket's identity and version coordinate instead of quoting it, judges every item, and turns an open correction request into a validator-enforced merge gate; scripts/requirement_contract.py reads tickets through pluggable adapters and reports drift.",
"skills": [
"./init",
"./prd",
"./adr",
"./migrate",
"./office-hours",
"./design",
"./plan-review-ceo",
"./plan-review-eng",
"./ship"
],
"author": {
"name": "choi88andys"
},
"license": "MIT",
"homepage": "https://github.com/choi88andys/skills",
"repository": "https://github.com/choi88andys/skills",
"keywords": [
"sdd",
"prWhat it installs
The manifest is a name and a version. 9 skills, 1 hook travel with it, and installing the plugin installs all of them — 1,346 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 5d ago Changed 7d34d8e2e853
- 18d ago Changed 948cb7706b6a
- 27d ago Changed 476b03755d07
- 28d ago Changed 9c0e9b529ee0
- 1mo ago Changed 8a29a563e6ee
- 1mo ago Changed · +14 lines c7055df5a1ee
- 2mo ago First seen · 32 lines scan A bf822a82dc76
immutable is a plugin published in the GitHub repository choi88andys/skills (9 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
git-sidebar
A lazygit-style side pane: every worktree of the repository and its local branches as rows you click. A worktree row moves the session there with /cd; a branch row shows its last commits and offers switch (clean tree only) or open worktree. Docked floor to ceiling beside the transcript in the fullscreen layout, above…
git
Git workflow tools: commits, PRs, review inbox, checkout, and work triage.
digest
Summarize AI-generated branches, PRs, and diffs into icon-rich cards, explain code state with git archaeology as self-contained HTML explainers, plus multi-project weekly recall digests.
git-pr
Committing, PR creation and review triage, and dependency upgrades.
code-quality
OxLint, Biome, and Prettier configuration, linting skills, and pre-commit hooks for consistent code quality.
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested, stacked PR or MR with agents.