Borrowing it
Nothing to install: this file belongs to Doyajin174/teguma. 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/Doyajin174/teguma/main/.agents/skills/repo-development-os/SKILL.mdgit clone --depth 1 https://github.com/Doyajin174/tegumaWrote 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/doyajin174/teguma/repo-development-os)<a href="https://agentmods.dev/skills/doyajin174/teguma/repo-development-os"><img src="https://agentmods.dev/badge/skills/doyajin174/teguma/repo-development-os/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/doyajin174/teguma/repo-development-os"><img src="https://agentmods.dev/badge/skills/doyajin174/teguma/repo-development-os.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.00037 | $0.01030 |
| Opus 5 | $0.00018 | $0.00515 |
| Sonnet 5 | $0.00007 | $0.00206 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
repo-development-os 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Development OS
Use existing Git, GitHub, Codex, and repository files. The routine is strict; its implementation is small. Do not add a daemon, hook, database, dashboard, scheduled scan, automatic fixer, global Codex state, or an all-in-one command.
Install
python3 <source-skill>/scripts/repo_os.py install --repo <path-inside-target-repo>
Installation adds the local skill, the managed AGENTS.md and pull-request blocks, and missing
starter files. It preserves project-specific text and can be rerun. Use --dry-run to preview.
Start every substantive task
python3 .agents/skills/repo-development-os/scripts/repo_os.py preflight --repo .
- Exit
0: required local and GitHub state was verified and no cleanup finding exists. - Exit
1: report the findings, clear them before new work, and rerun preflight. - Exit
2: required state could not be verified; report the gap and stop.
Preflight only reads the selected repository. It never mutates Git, GitHub, issues, pull requests, tags, releases, or worktrees.
Practical routing
- Prioritize the user's observable completion scenario and smooth real use. Keep planning and implementation to the smallest sufficient scope, but never skip, combine, or reorder a mandatory routine step.
- Load and follow
tidywithout waiting for the user to name it when the task's actual goal is repository-wide structure, governance, documentation conventions, duplication, or cleanup. Do not attach a broad tidy pass to ordinary feature or fix work, and do not expand the issue scope. - When
docs/code-atlasexists and work locates or changes a mapped concept, load and followmaintain-code-atlaswithout waiting for the user to name it. Revalidate current sources first and update only directly affected cards during authorized implementation. Never bulk-create or refresh unrelated cards.
Normal sequence
- Use one issue containing a Goal, Completion scenario, and measurable Acceptance criteria.
- Check current code and pull requests, research authoritative internet sources, and write a compact specification.
- Use one
codex/issue-N-slugbranch and one clean linked worktree under the stable sibling root. Update frommainbefore measurement. - Implement the smallest change that satisfies the issue.
- Open one human-readable pull request. It closes at most 3 issues, changes at most 50 files, uses
#Nin every change commit, and containsCloses #N. - Read the full diff once for self-review.
- Run one independent read-only AI review.
- Apply one fixup round when findings exist and rerun relevant checks.
- Squash merge.
- Update
main, remove the issue worktree and branch, confirm issue closure, and decide release.
What ships with it
10 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.
- agents/openai.yaml 292 B
- assets/repository/.github/ISSUE_TEMPLATE/development.yml 1.1 KB
- assets/repository/AGENTS.block.md 2.9 KB
- assets/repository/CHANGELOG.md 98 B
- assets/repository/docs/operations/DEVELOPMENT_RUNBOOK.md 378 B
- assets/repository/docs/retrospectives/TEMPLATE.md 190 B
- assets/repository/GITIGNORE.block 33 B
- assets/repository/PULL_REQUEST_TEMPLATE.block.md 832 B
- scripts/repo_os.py 38 KB runs code
- tests/test_repo_os.py 16 KB runs code
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 · 102 lines · 37 tokens per session scan A 251113af368f
repo-development-os is a skill published in the GitHub repository Doyajin174/teguma (0 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 1,030 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-31.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.