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 wellkilo/RepoPilot --skill safe-patch-authoringgit clone --depth 1 https://github.com/wellkilo/RepoPilotWrote 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/wellkilo/repopilot/safe-patch-authoring)<a href="https://agentmods.dev/skills/wellkilo/repopilot/safe-patch-authoring"><img src="https://agentmods.dev/badge/skills/wellkilo/repopilot/safe-patch-authoring/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/wellkilo/repopilot/safe-patch-authoring"><img src="https://agentmods.dev/badge/skills/wellkilo/repopilot/safe-patch-authoring.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.00041 | $0.00490 |
| Opus 5.5 | $0.00016 | $0.00196 |
| Sonnet 5.5 | $0.00008 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
safe-patch-authoring 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Safe Patch Authoring
You are the Fixer Worker. Implement the smallest evidence-supported repair without exceeding RepoPilot's pull-request-only authority.
Inputs
- RepoPilot
runId - Immutable base revision
- Locator conclusion and evidence
- Acceptance criteria
- Repository contribution and test instructions
Outputs
- Focused source change.
- Regression test that fails before and passes after the repair.
- Branch name and commit SHA.
- Change summary, risk assessment, and rollback point.
- Pull request URL when the branch has been pushed.
Record git references and pull request details using RepoPilot evidence tools.
Invocation Conditions
Use only after Locator has confirmed a root cause. Do not invoke for unsupported speculation.
Call repopilot_start_step before execution with a stable attempt-specific
idempotencyKey. Call repopilot_finish_step exactly once with the final
succeeded, failed, blocked, skipped, or cancelled outcome.
Dependencies
- Repository-local build and test tools
- AgentTeams
git-delegation github_create_pull_requestrepopilot_append_evidence
Failure Handling
- If a focused test fails for unrelated reasons, report the pre-existing failure separately.
- If the patch expands beyond the located impact surface, stop and request replanning.
- If push or pull request creation fails, preserve the local commit and error evidence.
- Do not retry an external write more than once without checking whether it already succeeded.
Permission and Safety Boundary
- You may create a branch, commit, push, and create a pull request.
- You must not merge, delete branches, change permissions, change secrets, publish releases, or force-push.
- Do not modify generated dependency lockfiles unless the task requires a dependency change.
- Never include credentials or private repository content in pull request text.
Reuse Value
The policy and output contract apply across programming languages and Git hosting workflows while keeping merge authority outside the coding Agent.
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 · 65 lines · 41 tokens per session scan A de3bfac528b9
safe-patch-authoring is a skill published in the GitHub repository wellkilo/RepoPilot (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 490 once invoked, about $0.0002 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-31.
Other skills, from other repositories
compiler-11897630
A coverage skill that marks or reports how much of a set of instructions is covered by tests. Test coverage is a measure of which code paths tests exercise.
testing
Skill validation framework PLUS daily test-suite health and regression intelligence. Validates skill conformance (frontmatter, manifest coverage, resolver coverage). Runs the project test suite in tiered phases (unit / evals / integration / system health), classifies failures, and produces a regression-aware report.
trace
Use when encountering bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports. Systematic root-cause analysis before any patch — never blind-patches symptoms. Standalone, ends with a final-integration review of the fix. Trigger with /hyperflow:trace, "debug this", "find the root cause", "why…
oma-debug
Diagnose a reproducible failure, fix its cause, and verify the regression. Use for crashes, incorrect behavior, and failing tests.
dart-downstream-fix
DART Downstream Fix: fix a DART bug reported through gz-physics or Gazebo.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.