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 agentmods add skills/opencoven/coven/codeflow-maintainernpx skills add OpenCoven/coven --skill codeflow-maintainergit clone --depth 1 https://github.com/OpenCoven/covenWrote 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/opencoven/coven/codeflow-maintainer)<a href="https://agentmods.dev/skills/opencoven/coven/codeflow-maintainer"><img src="https://agentmods.dev/badge/skills/opencoven/coven/codeflow-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 | $0.00039 | $0.01323 |
| Opus 5 | $0.00019 | $0.00661 |
| Sonnet 5 | $0.00008 | $0.00265 |
| Haiku 4.5 | $0.00004 | $0.00132 |
Grade A, and why
codeflow-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 4d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodeFlow Maintainer Skill
Source of Truth
PR_WORKFLOW.md: https://github.com/openclaw/maintainers/blob/main/.agents/skills/PR_WORKFLOW.md
This skill is OpenClaw-only. It implements the workflow defined in
openclaw/maintainers for OpenClaw repositories. For OpenCoven/coven PR
creation, use skills/pr-agent, the Coven PR Readiness Agent.
Working Rule
Skills execute workflow. Maintainers provide judgment. Always pause between skills to evaluate technical direction, not just command success.
Workflow Modes
1. Triage
Purpose: Assess whether PR is worth reviewing.
Focus:
- Is the problem statement clear?
- Does a realistic verification path exist?
- Is this PR worth our time?
- Are there duplicates?
Recommendation: Proceed to Review, Request Info, or Close.
Agent prompt:
[Mode: TRIAGE] Assess whether this PR is worth reviewing.
Focus on problem clarity, scope match, duplicate detection.
DO NOT suggest code changes, approvals, or merges.
2. Review (review-pr)
Purpose: Review only — produce findings and recommendation. DO NOT modify code.
Quality bar:
- Do not trust PR code by default
- Keep types strict (no
any) - Evaluate security impact and abuse paths
- Understand the system before changing it
Finding severities:
BLOCKER— must fix before prepareIMPORTANT— must fix before prepareMINOR— should fix (optional)NOTE— informational only
Artifacts: .local/review.md, .local/review.json
Checkpoint before advancing:
- What problem are they trying to solve?
- What is the most optimal implementation?
- Can we fix up everything?
- Do we have any questions?
Agent prompt:
[Mode: REVIEW] Produce findings, DO NOT modify code.
Focus: correctness, security, tests, types, scope, hardening.
Severity: BLOCKER > IMPORTANT > MINOR > NOTE.
Recommendation: READY FOR PREPARE, NEEDS WORK, NEEDS DISCUSSION, or CLOSE.
3. Prepare (prepare-pr)
Purpose: Make PR merge-ready on its head branch.
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.
- 4d ago First seen · 178 lines · 39 tokens per session scan A 6109b0b34b95
codeflow-maintainer is a skill published in the GitHub repository OpenCoven/coven (46 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 1,323 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-30.
Other skills, from other repositories
github
GitHub workflow — creating and managing repos, always working on feature/development branches (never committing core changes directly to main), PR conventions, branch protection, and gh CLI patterns.
github-cli
Automate GitHub workflows using the gh CLI for pull requests, issues, releases, actions, and repository management. Use when interacting with GitHub beyond basic git operations.
create-pr
Creates GitHub pull requests with pre-flight validation, conventional title formatting, and structured summary generation. Runs parallel checks (tests, lint, type-check, security) before opening. Supports feature, bugfix, refactor, and hotfix PR types with milestone assignment via gh CLI. Invoke only if the operator…
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.
issue-progress-tracking
GitHub issue workflow ceremony using gh CLI — labels issues as in-progress, creates feature branches (issue/N-description), commits with issue references, posts progress comments, and links PRs with Closes #N. Keeps issues in sync with development work. Use when starting work on an issue, tracking progress, or…
pr-triage
PR triage: audit open PRs, deep review selected ones, draft and post review comments. Args: "all" to review all, PR numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.