pr-factory-scout

pr-factory-scout is a skill for Claude Code, Codex from Atman36/codex-maintainer-kit. It costs 108 tokens per session (1,178 once invoked), scanned A, original, MIT.

A quick repository assessment guide for finding small, safe improvements suitable for automated pull requests. A repository is the project directory containing its code, history, and configuration.

In plain words
What is it for?
Reviewing documentation and tooling, checking CI and tests, assessing repository maturity, and producing three to seven low-risk improvement candidates with verification plans.
Why use it?
It reduces the time spent understanding an unfamiliar project and avoids proposing risky changes before checking its tests, tools, and conventions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Reviewing documentation and tooling, checking CI and tests, assessing repository maturity, and producing three to seven low-risk improvement candidates with verification plans.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/atman36/codex-maintainer-kit/pr-factory-scout
Install

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.

Any agent
npx skills add Atman36/codex-maintainer-kit --skill pr-factory-scout
Clone the repo
git clone --depth 1 https://github.com/Atman36/codex-maintainer-kit

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for pr-factory-scout

README.md
[![agentmods](https://agentmods.dev/badge/skills/atman36/codex-maintainer-kit/pr-factory-scout.svg)](https://agentmods.dev/skills/atman36/codex-maintainer-kit/pr-factory-scout)
Your own site
<a href="https://agentmods.dev/skills/atman36/codex-maintainer-kit/pr-factory-scout"><img src="https://agentmods.dev/badge/skills/atman36/codex-maintainer-kit/pr-factory-scout.svg" alt="Measured on agentmods" height="20"></a>
Per session 108 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,178 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00108 $0.01178
Opus 5 $0.00054 $0.00589
Sonnet 5 $0.00022 $0.00236
Haiku 4.5 $0.00011 $0.00118

Measured 7d ago against content hash b12fdd4cdbde, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

pr-factory-scout 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.

skills/pr-factory-scout/SKILL.md · 138 lines

How it starts

The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Role: Scout

Quick repository assessment and mergeable candidate discovery.

Inputs

  • {{REPO_ROOT}} - Local repository path
  • {{REPO_URL}} - Repository URL
  • {{BASE_BRANCH}} - Target branch (e.g., "main", "master")

Goal

Quickly decide whether this repo is a good target right now, and list 3–7 mergeable improvement candidates.

Process

  1. Read documentation: README, CONTRIBUTING, CODE_OF_CONDUCT, LICENSE
  2. Identify tooling: How to run tests, lint, build (if present)
    • Also map detected config paths (eslint, prettier, pytest.ini, tox.ini, tsconfig, CI workflows, etc.)
  3. Check repo signals: CI config exists? tests folder? recent commits? (local analysis only, don't browse web)
  4. Generate candidates: 3-7 low-risk improvements with title, type, estimated LOC, likely files, risk, verification plan

For detailed guidance on repo signals and scoring heuristics, see references/repo-signals.md.

Rules

  • Be stack-agnostic: Infer conventions from the repo; don't assume any framework
  • Prefer small, low-risk PRs: docs/tests/bugfix/CI/DX. Avoid "refactor everything"
  • Respect existing tooling: Follow CONTRIBUTING.md and existing tools. Don't suggest adding new deps unless unavoidable
  • Schema-valid JSON payload: Build payload conforming to ExecutionResult
  • Persist analysis JSON: Write payload to {{ARTIFACT_DIR}}/scout-<timestamp>.json
  • Chat output format: Return only SAVED_JSON_PATH=<absolute_path_to_json>
  • Put all findings under data: Keep structured results in the data field

Output Format

  1. Build JSON conforming to ../../schemas/execution_result.schema.json:
{
  "schema_version": "1.0",
  "id": "scout-<timestamp>",
  "stage": "scout",
  "status": "success",
  "summary": "Found 5 low-risk candidates in active repo with CI/tests",
  "started_at": "2024-01-15T10:30:00Z",
  "finished_at": "2024-01-15T10:32:00Z",
  "exit_code": 0,
  "artifacts": [],
  "metrics": {
    "duration_ms": 120000,
    "cost_usd": 0.05,
    "tokens_in": 15000,
    "tokens_out": 3000
  },
  "errors": [],
  "warnings": [],
  "data": {
    "repo_profile": {
      "stack_hints": ["typescript", "react", "jest"],
      "ci_detected": ["github-actions"],
      "commands": {
        "test": "npm test",
        "lint": "npm run lint",
        "build": "npm run build"
      },
      "config_paths": {
        "test": ["pytest.ini"],
        "lint": [".eslintrc.json"],
        "build": ["package.json"],
        "ci": [".github/workflows/ci.yml"]
      },
      "constraints_from_contributing": [
        "Run tests before submitting PR",
        "Follow conventional commits format"
      ]
    },
    "candidates": [
      {
        "id": "cand-1",
        "title": "Add missing test for edge case in parseURL",
        "change_type": "test",
        "risk": "low",
        "est_loc": 15,
        "likely_paths": ["src/utils/parseURL.test.ts"],
        "rationale": "Function has 80% coverage, missing edge case for malformed URLs",
        "test_plan": ["npm test", "Check coverage report"]
      }
    ],
    "repo_score": {
      "score_0_10": 8,
      "reasons": [
        "Active maintenance (commits in last week)",
        "CI/CD present",
        "Test suite exists",
        "Clear contributing guidelines"
      ],
      "blockers": []
    }
  }
}

Read the full file on GitHub · 138 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 7d ago First seen · 138 lines · 108 tokens per session scan A b12fdd4cdbde

Subscribe to this mod's changes

pr-factory-scout is a skill published in the GitHub repository Atman36/codex-maintainer-kit (2 stars, last pushed 3mo ago), licensed MIT. It adds 108 tokens to every session and 1,178 once invoked, about $0.0005 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.

Related

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…

The01Geek/prflow · 106 tokens

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…

The01Geek/prflow · 105 tokens

pr-description

Use when generating or updating a PR description for the current branch. Takes an optional issue number as argument.

The01Geek/prflow · 24 tokens

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…

The01Geek/prflow · 91 tokens

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.

vincentkoc/dotskills · 68 tokens

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…

The01Geek/prflow · 97 tokens