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/gtrabanco/agentic-workflow/bump-skillnpx skills add gtrabanco/agentic-workflow --skill bump-skillgit clone --depth 1 https://github.com/gtrabanco/agentic-workflowWrote 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/gtrabanco/agentic-workflow/bump-skill)<a href="https://agentmods.dev/skills/gtrabanco/agentic-workflow/bump-skill"><img src="https://agentmods.dev/badge/skills/gtrabanco/agentic-workflow/bump-skill.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.00062 | $0.01122 |
| Opus 5 | $0.00031 | $0.00561 |
| Sonnet 5 | $0.00012 | $0.00224 |
| Haiku 4.5 | $0.00006 | $0.00112 |
Grade A, and why
bump-skill 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 4d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Turn contract — verify before ending the turn
✓ Every changed skill's version: was bumped and BOTH changelogs got their rows
✓ The lint results (all 7 authoring rules, including the two machine-surface
parity/ordering checks and the internal-skill discovery-exclusion check)
were reported
✓ The git add + commit command block is printed as the ABSOLUTE last output
About to end the turn with any box unchecked? The turn is NOT done — complete the missing box first.
When to use
After any edit to one or more skills/<name>/SKILL.md files in this repo,
before committing. Handles the full documentation surface so nothing drifts.
Step 0 — Orientation
This skill is specific to the agentic-workflow repository. Before doing
anything, confirm you are in that repo (presence of skills/ + CHANGELOG.md
CHANGELOG.es.md). If not, stop and tell the user.
Versioning policy (from CHANGELOG.md):
| Bump | When |
|---|---|
| major | rename, removed/renamed flag, changed contract or output shape — ships with a migration note |
| minor | new backward-compatible capability: new flag, new section, new routing case |
| patch | wording, examples, clarifications, internal tidy — no behavior change |
Process
Progressive loading
The reference allowlist is exactly the two paths below. After orientation:
- Read change discovery and authoring lint.
- For every discovered skill, read version and documentation sync.
- Then print the summary below.
Both resources are normative and one hop from this file. Missing resource → stop; never guess a bump or skip a synchronization surface.
10. Print a summary and the next step
Print a table:
skill old → new bump
─────────────────────────────────────────
execute-phase 1.2.0 → 1.3.0 minor
plan-fix 1.0.1 → 1.0.2 patch
Then print the next step:
All documentation updated. Stage and commit:
git add skills/<name>/SKILL.md CHANGELOG.md CHANGELOG.es.md README.md README.es.md git commit -m "chore(skills): bump <name> to <version> — <one-line reason>"If this is a major bump with a migration note, also add
docs/workflow/MIGRATION.md.
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.
- 4d ago First seen · 121 lines · 62 tokens per session scan A 454cddd6699d
bump-skill is a skill published in the GitHub repository gtrabanco/agentic-workflow (20 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 1,122 once invoked, about $0.0003 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
offensive-mitigations
Security mitigation reference and bypass catalog: ASLR, DEP/NX, RELRO, stack canaries, CFI, sandboxing, seccomp. Covers both detection of enabled mitigations and known bypass techniques. Use when assessing target hardening or planning exploit mitigation bypasses.
offensive-exploit-development
Exploit development operational guide: environment setup, debugging workflow, PoC development lifecycle, writing reliable exploits, using pwntools/pwndbg, heap exploitation techniques, and weaponization considerations. Use when actively developing exploits or setting up an exploit dev environment.
offensive-advanced-redteam
Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC…
offensive-dependency-confusion
Deep-dive offensive methodology for dependency confusion and namespace attacks across all major package ecosystems. Covers npm scope confusion exploiting the gap between public and private scoped packages and .npmrc misconfigurations where registry mappings fail to pin internal scopes exclusively. Addresses PyPI…
offensive-phishing
Phishing campaign execution methodology for authorized red team engagements. Covers end-to-end campaign lifecycle: infrastructure provisioning (GoPhish, SMTP relay configuration, domain acquisition and aging, SPF/DKIM/DMARC alignment), payload delivery vectors (Office macro weaponization, HTA droppers, ISO/IMG…
offensive-active-directory
Active Directory attack methodology for internal network red team engagements. Covers reconnaissance (BloodHound, PowerView, ADExplorer), credential abuse (Kerberoasting, ASREProasting, NTLM relay, LLMNR/NBT-NS poisoning), privilege escalation (ACL abuse, GPO abuse, unconstrained/constrained delegation), lateral…