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 jonathanmr22/pact --skill pact-buggit clone --depth 1 https://github.com/jonathanmr22/pactWrote 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/jonathanmr22/pact/pact-bug)<a href="https://agentmods.dev/skills/jonathanmr22/pact/pact-bug"><img src="https://agentmods.dev/badge/skills/jonathanmr22/pact/pact-bug/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/jonathanmr22/pact/pact-bug"><img src="https://agentmods.dev/badge/skills/jonathanmr22/pact/pact-bug.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.00011 | $0.00301 |
| Opus 5.5 | $0.00004 | $0.00120 |
| Sonnet 5.5 | $0.00002 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
pact-bug 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.
What it actually says
Create or update a PACT bug tracking file. Follow this protocol:
Step 1: Check existing solutions first.
Read bugs/_SOLUTIONS.yaml and search for matching tags. If a previous session already solved this class of bug, report the existing solution instead of re-investigating.
Step 2: Create the bug file.
If no existing solution matches, create bugs/{system}/{system}-NNN.yaml with:
id,title,status: investigating,severity,system,tagssymptom— what was observedexpected— what should happeninvestigation— log every attempt in real time (attempt number, what was tried, result)
Step 3: Update as you investigate. Add each attempt to the investigation log as you try things. Failed attempts are as valuable as successes — they prevent the next session from wasting hours on dead ends.
Step 4: When fixed, complete the record.
Update status: fixed, add root_cause, fix, files_changed, and prevention.
Step 5: Graduate reusable solutions.
If the fix applies to a class of bugs (not just this specific instance), add an entry to bugs/_SOLUTIONS.yaml with tags for future matching.
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 · 26 lines · 11 tokens per session scan A 9749aaef9f71
pact-bug is a skill published in the GitHub repository jonathanmr22/pact (15 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 301 once invoked, about $0.0000 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-08-30.
Other skills, from other repositories
issue-debugging
Systematic methodology for issue debugging including root cause analysis, impact mapping, tiered validation plans, and confidence assessment. Use when analyzing bugs, fixing issues, or validating fixes.
fix-bug
Run the Fix Validation pipeline to investigate, fix, and validate a bug. Ensures deterministic pipeline execution with IssueAnalyzer, FixWriter, TestWriter (conditional), TestAudit (conditional), and FixValidator stages.
concurrency-and-async
Use when a ticket involves work happening at the same time — async/await flows, promises and futures, goroutines and channels, threads and locks, parallel requests, races, deadlocks, "sometimes it double-processes" — and the change must be correct under interleaving, not just on the happy sequence. Invoke for any…
concurrency-review
Use as a REVIEW LENS when judging another agent's diff for concurrency and data-integrity defects under failure — concurrent writers, unsynchronised read-modify-write and lost updates, temp-file name collisions, non-atomic file writes, cross-process locking and stale-lock leases, crash/pause/retry schedules…
incident-response
Use when a production incident has been declared and needs classification, triage, escalation, and post-mortem. Covers SEV1-SEV4 severity, false-positive filtering, NIST SP 800-61 lifecycle, and blameless post-mortem facilitation. For proactive threat hunting before an incident fires, use threat-detection. For cloud…
error-handling
Use when a ticket touches how failures are represented, propagated, or reported — a new error type, a retry, a fallback, "handle the case where X fails", swallowed exceptions, or unclear error messages — and the result must fail loudly where it should and recover only where it can. Invoke for "handle errors properly"…