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 goiltpatpat/patpat --skill patpat-changegit clone --depth 1 https://github.com/goiltpatpat/patpatWrote 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/goiltpatpat/patpat/patpat-change)<a href="https://agentmods.dev/skills/goiltpatpat/patpat/patpat-change"><img src="https://agentmods.dev/badge/skills/goiltpatpat/patpat/patpat-change/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/goiltpatpat/patpat/patpat-change"><img src="https://agentmods.dev/badge/skills/goiltpatpat/patpat/patpat-change.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.00038 | $0.00568 |
| Opus 5 | $0.00019 | $0.00284 |
| Sonnet 5 | $0.00008 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
patpat-change 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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Patpat Change
For clear, bounded, reversible local work without delivery intent, use this skill and its relevant references. Otherwise read the operating protocol and execution graph in full before acting. Escalate on uncertainty, security, auth, billing, secrets, architecture, cross-cutting work, or delivery intent. Do not load the router or reread unchanged instructions already loaded in this session.
Read smallest safe change, preserve safety, and proof over proxy. Apply the bounded change playbook.
For a behavior-preserving rename, move, extraction, inline, or deduplication, apply the behavior-preserving refactor playbook. When the user requests test-first work or a cheap deterministic regression target exists, apply regression first.
When regression-first applies, observe fail-before (or an explicit why-not) and report fail-before and pass-after on the same check; do not silently skip.
For an explicit visual migration or pixel-equivalence claim, apply the visual equivalence playbook without weakening its baseline or comparison harness.
Inspect version-control state and nearby contracts before editing. Define Claim, Surface, Action, Expect, and Cleanup. Make one coherent repository-native patch. Avoid unrelated cleanup, speculative abstractions, new dependencies, and public interface changes unless the objective requires them.
Do not claim completion from generation, compilation, or tests alone when the changed behavior has an observable surface.
Proof closure
Define the five-field proof contract before any mutation. Close mutating work with:
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 Changed · +2 lines 4331b83a5c07
- 7d ago Changed · +2 lines 06b8027bf82a
- 11d ago First seen · 26 lines · 38 tokens per session scan A 738febd032c3
patpat-change is a skill published in the GitHub repository goiltpatpat/patpat (1 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 568 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-31.
Other skills, from other repositories
Repository Knowledge Management
Create and maintain the Repository Knowledge Base using the official Agentic Engineering playbooks.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
requirements-authoring
To author, update, and validate functional/non-functional requirements as atomic units with user approval.
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
ijfw-workflow
Use when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.
ijfw-plan
Use when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by…