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.
npx skills add photostructure/coding-skills --skill stagegit 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/skills/photostructure/coding-skills/stage)<a href="https://agentmods.dev/skills/photostructure/coding-skills/stage"><img src="https://agentmods.dev/badge/skills/photostructure/coding-skills/stage/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/photostructure/coding-skills/stage"><img src="https://agentmods.dev/badge/skills/photostructure/coding-skills/stage.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.00037 | $0.02755 |
| Opus 5.5 | $0.00015 | $0.01102 |
| Sonnet 5.5 | $0.00007 | $0.00551 |
| Haiku 4.5 | $0.00004 | $0.00276 |
Grade A, and why
stage 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 14d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stage Session Changes
More on these workflows: photostructure.com/coding (no dedicated
stagearticle yet)
Stage ONLY the changes that belong to the current body of work and compose a Conventional Commit message.
User direction
User instructions take precedence over this skill's workflow defaults. A direct instruction such as "commit", "approved, commit", or "commit these changes" authorizes the commit for the understood scope. Use the supplied message or compose one; the user need not approve its exact wording separately.
Unless the user also requests a review first, verify the staged scope and commit without starting or resuming a review, requiring a reviewer verdict, or asking for approval again. Loading this skill does not reopen settled decisions about scope, grouping, or review. Preserve unrelated changes and follow the repository's Git history safeguards. Ask for clarification only when the commit scope cannot be determined from the conversation and repository state.
When project instructions require review before every commit, a commit instruction for changes that review has not finished on since they last changed runs the review first, and only an explicit instruction to skip review skips it.
If, after checking the current git status, you find that all of your changes have been committed already, tell the user that: this skill is done.
NEVER git add an entire modified file unless every hunk in its diff belongs to this work.
Interactive staging may be unavailable. This skill includes
scripts/stage_hunks.py for deterministic,
non-interactive partial staging on Windows and POSIX hosts.
One concern per commit
When preparing a commit proposal, propose separate commits for distinct concerns unless the user has already specified or approved their grouping.
Signs the session's work should be split:
- Changes span unrelated features, bugs, or subsystems (e.g. a CSS tweak + an unrelated backend fix)
- You'd need "and" in the commit subject to describe it (
fix X and refactor Y) - The commit message would exceed 10 lines to explain everything
- Some changes are refactors/cleanup while others are behavior changes
- Tests for feature A are mixed with implementation of feature B
What ships with it
2 files 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.
- 14d ago Changed · +5 lines 807b11d48aa0
- 28d ago Changed c5eaa5447600
- 1mo ago Changed · +21 lines e3f15b3c41ca
- 1mo ago Changed · +2 lines 61783264b17c
- 1mo ago First seen · 222 lines · 37 tokens per session scan A 321452a05d31
stage is a skill published in the GitHub repository photostructure/coding-skills (4 stars, last pushed 13d ago), licensed MIT. It adds 37 tokens to every session and 2,755 once invoked, about $0.0001 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-31.
Other skills, from other repositories
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
signing-preflight
Before the first commit of a session, check that commit signing will work — the key is loaded and unlocked — and ask the operator to unlock it once, up front, instead of discovering it after a hundred unsigned commits. Never disables signing silently, never re-signs history without asking. Use at the start of…
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
git-commit
Creates git commits following Conventional Commits format with type/scope/subject. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md.
phx-watch-pr
Watch an Elixir/Phoenix PR with an Amp Orb keep-alive lease until required non-deployment CI is green and review threads are resolved.