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 agentmods add skills/transilienceai/communitytools/skill-updatenpx skills add transilienceai/communitytools --skill skill-updategit clone --depth 1 https://github.com/transilienceai/communitytoolsWrote 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/transilienceai/communitytools/skill-update)<a href="https://agentmods.dev/skills/transilienceai/communitytools/skill-update"><img src="https://agentmods.dev/badge/skills/transilienceai/communitytools/skill-update.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.01188 |
| Opus 5 | $0.00018 | $0.00594 |
| Sonnet 5 | $0.00007 | $0.00238 |
| Haiku 4.5 | $0.00004 | $0.00119 |
Grade A, and why
skill-update 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Update
Generate or refine Claude Code skills following Anthropic best practices.
Hard caps (enforced by scripts/skill_linter.py)
SKILL.md≤ 150 linesreference/*.md≤ 200 lines (reference/scenarios/*.md≤ 400 lines)README.md≤ 100 lines- Every
SKILL.mdhas YAML frontmatter withname+description - No
DO NOT/MUST NOT/NEVERoutside an## Anti-Patternssection - No challenge-specific identifiers (machine names, lab IDs, lab IPs, preserved flags)
- Every Markdown link resolves to an existing file
- Every reference file is linked from at least one other file (no orphans)
Principles
- Brevity first. Every file short, simple, human-readable. Challenge every token.
- Progressive disclosure. SKILL.md navigates;
reference/holds detail;reference/scenarios/holds concrete exploit flows. - Separation of concern. SKILL.md = WHAT + when.
reference/role-*.md= HOW agents behave when spawned. - Single canonical home for any cross-cutting rule (output discipline, credential loading, brute-force, etc.). Other files reference, never restate.
File structure
skills/<skill-name>/
├── SKILL.md # ≤150 lines, YAML + navigation
├── reference/
│ ├── *-principles.md # ≤150 lines (decision tree)
│ ├── INDEX.md
│ ├── *.md # patterns, ≤200 lines
│ └── scenarios/
│ └── <category>/
│ └── *.md # ≤400 lines, self-contained
└── README.md # optional, ≤100 lines
SKILL.md template
---
name: <skill-name>
description: What it does AND when to use. Include trigger phrases.
---
# <Skill Name>
<one-paragraph scope>
## When to use
- <bullet>
## Workflow / Quick start
<≤30 lines>
## References
- [reference/...](reference/...)
## Anti-Patterns
- <when negative framing is genuinely needed, put it here>
Run it
The procedure is a workflow — every step is code-enforced, so none can be skipped.
Workflow('skill-update', { output_dir: 'projects/<engagement>' }) // harvest an engagement
Workflow('skill-update', { learnings: [{ text, technique_type }] }) // judge a known set
Workflow('skill-update', { mode: 'audit' }) // read-only, writes nothing
What ships with it
4 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.
- 5d ago First seen · 126 lines · 36 tokens per session scan A 5684c5ecfcb8
skill-update is a skill published in the GitHub repository transilienceai/communitytools (509 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 1,188 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
pentester-playwright
Phases 1b/3/4 authorized browser automation — SPA recon, multi-role auth, route/API catalog, PoC screenshots, Evidence landing (scoped proxy). Skill-gate read for web phases. Use when Phase 1b/3/4 web work, JS-rendered SPA, real browser needed, HAR/network capture, or Playwright PoC evidence.
osint-recon
Phase 1 conditional OSINT depth — four-dimension model (server→site→domain→people; people is conditional). Skill-gate companion to pentester-enum-services / pentester-recon. Use for passive OSINT depth, full recon dimensions, author tracking, not as Phase 0/Schema replacement.
pentester-exploit
Phase 4 exploitation — PoC construction, exploit-db/msf search, safe verification. Required Skill-gate read at Phase 4. Use when starting Phase 4, exploitation, exploit, PoC, exploit-db, msf, Metasploit, or payload delivery.
pentester-toolkit
Provision the pinned pentest toolset via DotSlash for the current scanenv (host-kali or kali-target-${ID}). Adapter, not a tool wrapper.
pentester-waf-bypass
Phase 4 conditional — WAF/filter bypass for authorized CTF/range/pentest when payloads are blocked. Use at Phase 4 if blocked, or when user mentions WAF bypass, filter evasion, SQL/XSS/command-injection bypass, or security filter analysis.
pentester-recon
Phase 1 intelligence recon methodology — passive+active recon, stack fingerprint, attack-surface map. Required Skill-gate read at Phase 1 (with pentester-enum-services). Use when starting Phase 1, intelligence gathering, recon, reconnaissance, OSINT prep, target profiling, or attack surface mapping.