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 Security-Phoenix-demo/security-skills-claude-code --skill tm-quick-security-assessmentgit clone --depth 1 https://github.com/Security-Phoenix-demo/security-skills-claude-codeWrote 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/security-phoenix-demo/security-skills-claude-code/tm-quick-security-assessment)<a href="https://agentmods.dev/skills/security-phoenix-demo/security-skills-claude-code/tm-quick-security-assessment"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/tm-quick-security-assessment/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/security-phoenix-demo/security-skills-claude-code/tm-quick-security-assessment"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/tm-quick-security-assessment.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.00125 | $0.01182 |
| Opus 5 | $0.00063 | $0.00591 |
| Sonnet 5 | $0.00025 | $0.00236 |
| Haiku 4.5 | $0.00013 | $0.00118 |
Grade A, and why
tm-quick-security-assessment 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 yesterday.
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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TM Security Assessment (quick tier)
Quick and change-scoped. This tier does NOT re-model the whole system or hunt the entire repo. It scopes to a git worktree / branch, diffs against a base, and assesses only the changed attack surface — fast enough to run on every branch before merge. It stays threat-model-aware: if a model exists it uses it to prioritise, but it does not build a full one.
Two tiers, pick by need:
- This skill (quick) — a branch/worktree diff pass; minutes; catches regressions and obvious bugs in what changed.
tm-security-review(comprehensive) — full threat model as input + deep whole-repo zeroday hunt with a PoC per finding. Escalate to it when this pass flags a design-level risk or the change touches a trust boundary.
It composes two sibling skills, scoped to the diff:
security-assessment(../security-assessment/SKILL.md) — OWASP Top 10 checks, run only over changed files.0day-scanner(../0day-scanner/SKILL.md) inlightmode — it is built for commit/PR/branch/diff analysis; drive it with the branch or diff.
When to use
- "quick security assessment on this branch/worktree", "pre-merge security check", "scan the diff"
- Fast, cheap, change-scoped — not a full audit
Inputs (ask; if user is away, default + label [ASSUMPTION])
- Worktree / branch: the branch or worktree path to assess. Default: current worktree's checked-out branch.
- Base: what to diff against. Default: the repo's default branch (
main/master), else the branch's merge-base. - Existing threat model? Optional. If a
*-threat-model.mdis available, use its trust boundaries to prioritise; do not build a new one here (that's the review's job). - Deployment/trust context (drives severity): self-hosted vs hosted multi-tenant; attacker vs operator.
Phase 0 — Establish scope (worktree / branch diff)
- Resolve the target branch and base. If the branch isn't checked out, create a throwaway worktree:
git worktree add <tmp> <branch>(remove it when done). - Compute the changed set:
git diff --name-only <base>...<branch>(three-dot = changes on the branch since it forked). Note added/modified files and any new entry points, routes, deps, or IaC. - Map the changed surface:
| Changed file | New/changed entry point or sink | Reaches a trust boundary? |. Pull trust boundaries from an existing threat model if provided; otherwise infer them quickly from the changed files (new HTTP handler, new subprocess/exec, new query, new deserialization, new external fetch).
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.
- yesterday First seen · 64 lines · 125 tokens per session scan A eedc94b29901
tm-quick-security-assessment is a skill published in the GitHub repository Security-Phoenix-demo/security-skills-claude-code (70 stars, last pushed yesterday), licensed MIT. It adds 125 tokens to every session and 1,182 once invoked, about $0.0006 per session on Opus 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-09-11.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…