Borrowing it
Nothing to install: this file belongs to Brad-Edwards/aptl. 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/Brad-Edwards/aptl/main/.claude/skills/stage/SKILL.mdgit clone --depth 1 https://github.com/Brad-Edwards/aptlWrote 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/brad-edwards/aptl/stage)<a href="https://agentmods.dev/skills/brad-edwards/aptl/stage"><img src="https://agentmods.dev/badge/skills/brad-edwards/aptl/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/brad-edwards/aptl/stage"><img src="https://agentmods.dev/badge/skills/brad-edwards/aptl/stage.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 Privilege Escalation · line 12 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00016 | $0.00261 |
| Opus 5.5 | $0.00006 | $0.00104 |
| Sonnet 5.5 | $0.00003 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
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 1mo 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
Stage Changes
Step 1: Identify Changed Files
- Run
git statusto see all changed and untracked files. - Exclude from staging: .env files, credentials, secrets, large binaries.
Step 2: Stage Files
git addall relevant changed files.
Step 3: Pre-commit Loop
Run up to 5 iterations:
- Run
pre-commit runagainst the staged files. Never use--all-fileslocally; CI/CD owns whole-tree checks. - If it passes, proceed to Step 4.
- If it fails:
- Read the failure output.
- Fix the issues.
- Re-stage any modified files with
git add. - Go back to step 1.
- If still failing after 5 attempts, report the failure details to the user and stop.
Step 4: Report
- List what is staged:
git diff --cached --name-only - Confirm pre-commit passes.
- "All files staged and pre-commit clean. Ready for commit."
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.
- 1mo ago Changed · +1 lines b139a52b1ccb
- 2mo ago First seen · 36 lines · 16 tokens per session scan A fad2a69469aa
stage is a skill published in the GitHub repository Brad-Edwards/aptl (25 stars, last pushed 24d ago), licensed MIT. It adds 16 tokens to every session and 261 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-30.
Other skills, from other repositories
re0-git
Rewrite a finished commit's message into a clean, handoff-ready form in your own log style, so git log alone tells the story. User-invoked: run it after a commit.
adk-git
Writes commit messages and pull request descriptions for the adk-python repository: Conventional Commits types and scopes, subject lines that say why a change was made, and the linked-issue and testing-plan sections the PR template requires. Use when writing or rewording a commit message, squashing commits before a…
commit-context
Trace a file, function, or line back to the agent session that produced its current commit. Use when the user asks "why is this code here", "what was the agent doing when this changed", "who wrote this", or wants context on a specific location in the codebase.
commit-history
List recent git commits linked to agent sessions, optionally filtered by branch or repo. Use when the user asks "show agent commits", "what has the agent shipped", "list linked commits", or wants commits with their session context.
resolve-publish
Commit the validated fix and follow local-only, workflow-owned, or direct PR publication.
commit-messages
Write git commit messages and pull request titles in the WARP format used by the swarms repo.