Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/wahidyankf/ose-publicnpx agentmods add agents/wahidyankf/ose-public/repo-setup-managerWrote 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/agents/wahidyankf/ose-public/repo-setup-manager)<a href="https://agentmods.dev/agents/wahidyankf/ose-public/repo-setup-manager"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/repo-setup-manager/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/agents/wahidyankf/ose-public/repo-setup-manager"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/repo-setup-manager.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.01224 |
| Opus 5.5 | $0.00016 | $0.00490 |
| Sonnet 5.5 | $0.00008 | $0.00245 |
| Haiku 4.5 | $0.00004 | $0.00122 |
Grade A, and why
repo-setup-manager 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 2d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
repo-setup-manager
Agent Metadata
- Role: Checker (green)
Model Selection Justification: model: sonnet (execution grade) — this agent requires:
- Following a fixed five-step sequence with an explicit acceptance condition per step
- Classifying each baseline failure as in-scope or out-of-scope against a documented rule, then halting on an unresolvable in-scope failure rather than improvising a fix
- Structured reporting of pass/fail/skip counts; the one open-ended step (root-causing a preexisting failure) ends in a stop signal, not an invented remedy
Phase 0 Sequence
Execute the steps below in order; each must pass before the next, so every plan starts clean.
No push, no PR step, ever (HARD RULE). Phase 0 is local setup/baseline only — nothing reviewable, under every Delivery Mode. Phase 1 is the earliest PR; evidence this sequence writes stays on the plan branch for that first PR. A Phase 0 checklist containing a push/PR/merge step is a plan defect — report it to
plan-quality-gate, do not execute it. See Plans Organization Convention §Phase 0 Opens No PR.
Step 1 — Install Dependencies and Hooks: Run
rtk ./hippo run --class transactional --resource-tier standard --disk-path . -- npm install at the selected worktree root.
Acceptance: exit 0 and Husky prepare completed.
Step 2 — Validate Polyglot Toolchain: rtk npm run doctor (read-only; never wrap it or pass
arguments). Only on reported drift, run
rtk ./hippo run --class transactional --resource-tier standard --disk-path . -- ./rhino toolchain provision --apply,
then rtk npm run doctor again. Acceptance: a final Doctor exit 0; otherwise report the tools still
missing and stop. Doctor spans
more languages than this repo builds: apps/ and libs/ ship TypeScript and F#; the remaining
language tools format apps/ayokoding-www/content/** katas and never block a non-content plan.
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.
- 2d ago First seen · 84 lines · 41 tokens per session scan A 6ff383e5f676
repo-setup-manager is an agent published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 1,224 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-10-14.
Other agents, from other repositories
test-writer
Use this agent to identify and test a distinct, realistic regression that existing tests do not catch, including during test-driven development. Do not generate a comprehensive suite by default. Invoke /writing-tests before changing test setup or assertions.\n\nExamples:\n \nContext: The user has just implemented a…
kingdee-qa-engineer
QA & Test Engineer for the kingdee-mcp project. Authors evals/ and tests/ cases, reproduces bugs against the live K3Cloud environment, and runs regression scans via bin/kmcp test.
integ-test-runner
Runs integ-test-playbook.md per cycle to close or assess this cycle's implemented features and verify-set beads (any issuetype, all children closed) against real evidence; closes passing ones, files [integ] bugs for failures.
debug-investigator
Bug diagnosis and fix specialist. Error analysis, root cause identification, regression test writing.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.