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-automationgit 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-automation)<a href="https://agentmods.dev/skills/goiltpatpat/patpat/patpat-automation"><img src="https://agentmods.dev/badge/skills/goiltpatpat/patpat/patpat-automation/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-automation"><img src="https://agentmods.dev/badge/skills/goiltpatpat/patpat/patpat-automation.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.00049 | $0.00453 |
| Opus 5 | $0.00024 | $0.00227 |
| Sonnet 5 | $0.00010 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
patpat-automation 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 7d 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.
What it actually says
Patpat Automation
When invoked directly, read the operating protocol and execution graph in full. Do not load the router.
Read boundary discipline, idempotent effects, and preserve safety. Apply the automation design playbook. For a named issue-source triage and reproduce loop, also apply the issue loop playbook. Do not copy a host automation pack or enable a scheduler.
Require a concrete provider, immutable trigger identity, trusted coordinator, exact allowed writes, secret source outside the repository, idempotency key, dedupe behavior, immediate preflight, bounded retries and cost, safe test surface, verifier, and kill switch. Require compensation when reversal is possible; otherwise name the irreversible boundary and fail before it when state or authority is uncertain. Fail closed when any write-critical field is missing: return a configuration checklist and do not produce runnable or enabled automation.
Keep external writes under one coordinator. Give workers no credentials, write tools, or posting instructions. Default generated automation to disabled and test it against a sandbox or dry-run surface.
Enabling, scheduling, posting, filing, publishing, or deployment requires explicit authority immediately before the action. A provider-triggered issue loop may open only a draft pull request by default. Ready-PR delivery requires separate fresh interactive delivery intent (not activation alone).
Proof closure
Close repository mutations through:
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.
- 7d ago Changed 7655de0be189
- 11d ago First seen · 24 lines · 49 tokens per session scan A 7a22c4385019
patpat-automation is a skill published in the GitHub repository goiltpatpat/patpat (1 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 453 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…