Borrowing it
Nothing to install: this file belongs to open-software-network/os-clovy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/open-software-network/os-clovy/main/.agents/skills/repo-build-pr/SKILL.mdgit clone --depth 1 https://github.com/open-software-network/os-clovyWrote 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/open-software-network/os-clovy/repo-build-pr)<a href="https://agentmods.dev/skills/open-software-network/os-clovy/repo-build-pr"><img src="https://agentmods.dev/badge/skills/open-software-network/os-clovy/repo-build-pr/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/open-software-network/os-clovy/repo-build-pr"><img src="https://agentmods.dev/badge/skills/open-software-network/os-clovy/repo-build-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 138 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 139 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 138 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 139 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Tool Misuse · line 233 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Agent Snooping · line 216 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00177 | $0.05955 |
| Opus 5 | $0.00088 | $0.02978 |
| Sonnet 5 | $0.00035 | $0.01191 |
| Haiku 4.5 | $0.00018 | $0.00596 |
Grade A, and why
repo-build-pr 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 10d 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo build PR
Use this skill for the end-to-end implementation loop in open-software-network/os-clovy. The goal is not only to make code changes. The goal is to understand the prompt, isolate the work in worktrees, ship a coherent PR, and run the automated review loop with judgment.
To hand this entire workflow to a different harness as orchestrator (e.g. dispatch a whole build to Codex from Claude Code, or vice versa), use the repo-orchestrate skill instead — it wraps this workflow in a per-harness runner with a stop-before-publish default.
Skill map
This is the repo's entry-point skill; it orchestrates and defers. Each fact lives in exactly one owner — load the owner at the step that needs it, never restate its commands here:
repo-review— pre-publish review battery: axes, per-harness runners, disposition triage, convergence loop.repo-delegate— single-brief implementation dispatch to another harness (the building block of the cross-harness implementer mode).repo-orchestrate— hand this whole workflow to another harness.agent-e2e-qa— live QA process: surface decision tree, video recording/compression, os-platform upload, PASS/FAIL/BLOCKED evidence format.browser-test-tauri-fe— browser-surface technique: fake Tauri IPC bridge, Playwright/CDP driving, screenshot suites, PR-embeddable GIFs.os-platform/os-task-prep— tracker reads, task diagnosis and enrichment (intake step 3).repo-retrospect— post-cycle: mine the session, PR threads, and user feedback for lessons and fold them into the owning skill files.
Intake
Treat everything after /repo-build-pr (or $repo-build-pr in Codex) as the build prompt. If the user did not use the literal command but asks to build, implement, ship, or fix something in the repo, use this skill anyway.
- Read the prompt carefully and restate the concrete objective, constraints, and likely affected surface area. A trailing implementer directive (
with codexin Claude Code,with claudein Codex) selects a cross-harness implementer — see Model orchestration. - Read repo instructions before editing:
AGENTS.md- any referenced project plan or spec relevant to the task
What ships with it
1 file 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.
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.
- 10d ago First seen · 303 lines · 177 tokens per session scan A 68b553964862
repo-build-pr is a skill published in the GitHub repository open-software-network/os-clovy (356 stars, last pushed today), licensed MIT. It adds 177 tokens to every session and 5,955 once invoked, about $0.0009 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
personal-commands
Edit hex.config.ts, not .hex-sdk. Config and installed dependencies execute with the user's normal permissions; use only trusted packages and avoid network, filesystem, environment, or subprocess access unless the requested command requires it. Run bun run check after editing.
hex-personal-commands
Configure HEX personal voice commands, voice-dictation control phrases, and deterministic transcript transformations. Use when the user wants to add or change commands or transformations for the HEX macOS voice app.
macparakeet-stt
Use when the user asks to transcribe audio or video, search MacParakeet's local speech library, retrieve cited transcript segments or knowledge cards, or inspect and manage saved meeting artifacts on macOS Apple Silicon.
murmur-mcp
Query Murmur's local read-only MCP server for gated, indexed knowledge — semantic + full-text search over meetings and notes, entity dossiers, structured transcripts, open-commitment rollups, and typed note-folder database queries. Prefer this over grepping raw vault files. Use when you need to find, retrieve, or…
murmur-vault
How to coexist with Murmur's notes in an Obsidian vault — note anatomy, front-matter keys, managed sections you must never edit, wikilink discipline, entity stubs, where files live, the locked-folder disappeared-file rule, and the add-freely/prefer-append coexistence contract. Use when reading, editing, or creating…
engine-conflict-resolve
Ask Sutando to resolve a conflicted update of a Sutando checkout. When pulling the latest release/main conflicts with local changes, Sutando reproduces the merge in a scratch git worktree, resolves the conflicts there, proposes the resolution to the owner, and fast-forwards the live checkout only after explicit…