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 Atman36/codex-maintainer-kit --skill pr-factory-maintainergit clone --depth 1 https://github.com/Atman36/codex-maintainer-kitWrote 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/atman36/codex-maintainer-kit/pr-factory-maintainer)<a href="https://agentmods.dev/skills/atman36/codex-maintainer-kit/pr-factory-maintainer"><img src="https://agentmods.dev/badge/skills/atman36/codex-maintainer-kit/pr-factory-maintainer.svg" alt="Measured on agentmods" 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.00053 | $0.00388 |
| Opus 5 | $0.00026 | $0.00194 |
| Sonnet 5 | $0.00011 | $0.00078 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
pr-factory-maintainer 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 6d 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
PR Factory Maintainer
Use this repo-local workflow for open-source maintenance tasks.
Workflow
- Read
program.mdand the relevant target-repository instructions. - Select
full,quick-win, orarchitecturemode. - Run analysis in order:
full: Scout -> Analyst -> Critic -> Gatekeeperquick-win: Scout -> Gatekeeperarchitecture: Architect -> Critic -> Gatekeeper
- Stop after Gatekeeper when the maintainer requests analysis only.
- For an approved PRSpec, run Implementer -> Reviewer -> PR Writer.
- Run Publisher only when the maintainer explicitly requests fork, push, or pull-request creation.
Safety rules
- Keep the selected change small and reviewable.
- Treat
schemas/prspec.schema.jsonas the approved file scope. - Return stage results that conform to
schemas/execution_result.schema.json. - Use
tools/quality_gate.pybefore handoff. - Preserve audit artifacts; do not claim files exist unless they were written.
- Prefer read-only Codex runs before granting write access.
Deterministic orchestration
For automated runs, use tools/run_pipeline.py with explicit --stage-command values. Do not present a shortened command that omits required stage commands. See tools/README.md.
Output
Return a concise maintainer-facing summary:
- selected mode and candidate;
- approved PRSpec scope;
- changed files and checks run, if implementation was requested;
- blockers or residual risks;
- publication status.
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.
- 6d ago First seen · 44 lines · 53 tokens per session scan A d09665ef2fac
pr-factory-maintainer is a skill published in the GitHub repository Atman36/codex-maintainer-kit (2 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 388 once invoked, about $0.0003 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
docs-release-notes
Use when a change needs a user-visible release-note, changelog, or changeset entry — "add a release note", "add a changeset for this", "what goes in the changelog?", "write up what shipped", "note this for the next release" — or when finalizing a branch whose customer-visible features, bug fixes, or UI changes should…
docs-sync-internal
Use when code changes on the current branch need matching internal or developer documentation — "update our internal docs", "the architecture docs are stale after this change", "document what I just changed", "do the dev docs still match the code?" — or as a pre-push check that developer docs track the code. Narrower…
pr-description
Use when generating or updating a PR description for the current branch. Takes an optional issue number as argument.
retrospective-audit
Stage B of /prflow:retrospective-weekly: given a most-recent-first subset of one recurring pattern's occurrence-PR context bundles (bounded by auditbundlecap), re-derive the root cause and return one JSON object carrying a ranked findings array (one to three sub-patterns) — no edits, no worktree. Invoked as a subagent…
docs
Use when documentation generally needs to catch up with a branch before pushing or merging, covering internal developer docs, external customer-facing docs, and release notes together — "update the docs", "do a docs pass before I merge", "make sure everything's documented". Prefer this when no single documentation…
openclaw-github-dedupe
Investigate a cluster of GitHub issues and PRs, determine canonical candidates, post duplicate/related status, preserve contributor credit, and execute cleanup actions. Supports autonomous mode for provided-link-only closeout, merge/fix follow-through, changelog, and post-merge issue/PR cleanup.