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/photostructure/coding-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/photostructure/coding-skills/coding)<a href="https://agentmods.dev/plugins/photostructure/coding-skills/coding"><img src="https://agentmods.dev/badge/plugins/photostructure/coding-skills/coding/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/photostructure/coding-skills/coding"><img src="https://agentmods.dev/badge/plugins/photostructure/coding-skills/coding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
coding 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 12d 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.
What it actually says
{
"name": "coding",
"version": "3.4.0",
"description": "Opinionated Claude Code workflow skills: clear and unambiguous technical writing (write-clearly), iterative planning (replan), proof-based code review (review, review-staged, second-opinion), disciplined Conventional-Commit staging (gitplan, stage), finding the session that wrote an uncommitted change (find), and the Technical Project Plan workflow (tpp, handoff, tpp-orchestrate).",
"author": {
"name": "Matthew McEachen",
"url": "https://photostructure.com/coding/"
},
"homepage": "https://photostructure.com/coding/",
"license": "MIT",
"keywords": [
"claude-code",
"skills",
"code-review",
"planning",
"git",
"conventional-commits",
"technical-writing",
"plain-language"
]
}
What it installs
The manifest is a name and a version. 11 skills travel with it, and installing the plugin installs all of them — 604 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill second-opinion A 64 tokens
- Skill stage A 37 tokens
- Skill find A 82 tokens
- Skill gitplan A 33 tokens
- Skill tpp-orchestrate A 75 tokens
- Skill replan A 22 tokens
- Skill review-staged A 51 tokens
- Skill write-clearly A 104 tokens
- Skill tpp A 55 tokens
- Skill handoff A 32 tokens
- Skill review A 49 tokens
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.
- 12d ago Changed ebaa4ec88280
- 14d ago Changed ee038b2d3cbd
- 18d ago Changed 14e75c27cb7d
- 21d ago Changed 86fff7c694ad
- 28d ago Changed bfb3a3078071
- 1mo ago Changed 44b86e2c4ff4
- 1mo ago Changed 594a3c173295
- 1mo ago First seen · 22 lines scan A 9f5db079cd95
coding is a plugin published in the GitHub repository photostructure/coding-skills (4 stars, last pushed 13d 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
privacy-guard
Keeps private infrastructure details out of public repositories. Ships the privacy-guard skill: session rules for what must never cross the public boundary, plus a per-repo pre-commit gate built on a gitignored local denylist and gitleaks. The denylist is never committed, so the hook is a no-op for external…
github-workflow
Git commit, PR creation, review, and merge skills following Conventional Commits.
github
Skills for GitHub pull request workflows — creating PRs, addressing review feedback, and resolving threads.
han-github
Github specific extensions to the Han plugin for agentic planning and coding. Provides skills to post code reviews as PR comments, update a PR description with a consistent format, etc.
manifest-dev-tools
Tools for prompts and PRs alongside the manifest workflow. Includes collaborative PR walkthroughs, autonomous PR review that independently re-verifies a manifest gate by gate, author-side PR babysitting that drives the lifecycle toward green and mergeable, gap-calibrated prompt engineering, standalone goals distilled…
odin-git
ODIN workflows for commits, branches, pull requests, review feedback, and issue tracking.