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 andreibesleaga/GABBE --skill pbt-strategygit clone --depth 1 https://github.com/andreibesleaga/GABBEWrote 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/andreibesleaga/gabbe/pbt-strategy)<a href="https://agentmods.dev/skills/andreibesleaga/gabbe/pbt-strategy"><img src="https://agentmods.dev/badge/skills/andreibesleaga/gabbe/pbt-strategy/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/andreibesleaga/gabbe/pbt-strategy"><img src="https://agentmods.dev/badge/skills/andreibesleaga/gabbe/pbt-strategy.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.00033 | $0.01884 |
| Opus 5.5 | $0.00013 | $0.00754 |
| Sonnet 5.5 | $0.00007 | $0.00377 |
| Haiku 4.5 | $0.00003 | $0.00188 |
Grade A, and why
pbt-strategy 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 First seen · 118 lines · 33 tokens per session scan A df709ac4ab3a
pbt-strategy is a skill published in the GitHub repository andreibesleaga/GABBE (23 stars, last pushed yesterday), with no licence file. It adds 33 tokens to every session and 1,884 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-09-04.
Other skills, from other repositories
python-testing
Guidelines for writing and running tests in the Agent Framework Python codebase. Use this when creating, modifying, or running tests.
test-driven-development
Writing code with tests first: RED-GREEN-REFACTOR, reproduce bugs as failing tests before fixing, and avoid testing anti-patterns. Use when implementing behaviour, fixing a defect, or asked to add tests.
parallel-yak-implementation
Use when multiple independent leaf yaks are ready to implement and can be worked on concurrently with separate agents in worktrees.
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.
investigate
Root-cause a bug, test failure, CI failure, or unexpected behavior before changing code. Reproduce, compare against working code, test one hypothesis at a time, then fix with a failing regression test first. Stops after three failed fixes to question the design, and requires fresh evidence before any "fixed" claim.…
feature-chain
Use when the user wants to build a new feature, implement a new capability, add functionality, or start a development task from scratch. Runs design Q&A → PRD → TDD → review automatically.