J
joshsegatt/SeniorOS
Claude Code, Codex & Google Antigravity skills and hooks that make coding agents prove their work:…
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"joshsegatt-senioros": {
"command": "npx",
"args": ["senioros"]
}
}
}Parsed from the README we fetched on 2026-10-27; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"joshsegatt-senioros": {
"command": "npx",
"args": ["senioros"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio joshsegatt-senioros -- npx senioros
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 3 ★ · joshsegatt/SeniorOS · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-27 · last seen 2026-11-14 · seen 20× · listed by 4 sources
- Score
- score 403 · 3 ★ · 4 sources · repo
- Install
npx senioros
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx senioros. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: Agent 技能. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
joshsegatt/SeniorOS；first catalogued 2026-10-27；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.SeniorOS is a portable engineering harness for coding agents.
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
It adds selective context, risk-aware execution, deterministic verification, durable project memory, and evidence-backed completion to agentic development workflows.
Results ·
Quick start ·
How it works ·
Vibe coders ·
Senior developers ·
Skills ·
Proof ·
Evals ·
Architecture
## Measured, not claimed
A live bench runs the same model on the same trap tasks with no pack, with Superpowers and with SeniorOS. Hidden tests and the repository state grade every run; no model judges another.
| Host and model | No pack | Superpowers | SeniorOS |
| Claude Code, Claude Haiku (17 tasks, 3 trials each) | 45/51 | 44/51 | 49/51 |
| Antigravity, Gemini Flash (4 hard tasks, 3 trials each) | not run | 8/12 | 12/12 |
| Antigravity, Gemini Flash (multi-regression refactor, 4 trials) | 0/4 | 0/4 | 4/4 |
In Claude Code, SeniorOS shipped no wrong code and never force-pushed main; Superpowers wrote wrong code three times (a refactor fixed only where a test pointed, a password-hash switch that locked out existing accounts). Every run, task and caveat (including which tasks were written alongside the changes they reward) is in evals/bench/, and you can rerun it with one command.
## Why SeniorOS exists
Coding agents can already generate a lot of code. The expensive failures usually happen around the code:
reading half the repository for a one-line change;
reading too little before touching auth, data, or infrastructure;
changing unrelated files because they looked “helpful”;
declaring success without running the project's real checks;
weakening tests instead of understanding the regression;
forgetting architectural decisions between sessions;
treating a button rename and a production migration with the same ritual.
SeniorOS treats these as engineering-system problems, not prompt-writing problems.
> The goal is not to make the model sound senior. The goal is to make the workflow behave like disciplined engineering.
## How it works
SeniorOS pushes agent work toward a risk-adaptive loop:
text
Goal Contract
Relevant Context
Risk Assessment
Right-Sized Execution
Proof
Review
Ship / Not Proven / Blocked
The important part is that not every task gets the same process.
| Task | SeniorOS behavior |
| Rename a button | Direct edit + proportionate verification |
| Add an API route | Light plan + relevant tests |
| Change authentication | Full context + security/risk review + proof |
| Production migration | Strict plan + rollback thinking + explicit boundaries |
| “Just make CI green” | Investigate root cause before weakening meaningful checks |
### The difference in one line
text
normal agent loop: request → generate → edit → "done"
SeniorOS loop: request → understand → assess → execute → prove → review → state what is known
SeniorOS prefers:
text
PROOF BASELINE: PASS
Residual risk: LOW
Skipped checks: none
instead of:
text
Everything looks good! 🚀
because optimism remains stubbornly absent from every serious test framework.
## Quick start
Requires Node.js 20 or newer. No clone needed: the CLI is published on npm as senioros, and its command is senior.
### 1. Install SeniorOS for your coding agent
Claude Code (recommended: the plugin adds the routing rules and the destructive-command guard):
Results ·
Quick start ·
How it works ·
Vibe coders ·
Senior developers ·
Skills ·
Proof ·
Evals ·
Architecture
## Measured, not claimed
A live bench runs the same model on the same trap tasks with no pack, with Superpowers and with SeniorOS. Hidden tests and the repository state grade every run; no model judges another.
| Host and model | No pack | Superpowers | SeniorOS |
| Claude Code, Claude Haiku (17 tasks, 3 trials each) | 45/51 | 44/51 | 49/51 |
| Antigravity, Gemini Flash (4 hard tasks, 3 trials each) | not run | 8/12 | 12/12 |
| Antigravity, Gemini Flash (multi-regression refactor, 4 trials) | 0/4 | 0/4 | 4/4 |
In Claude Code, SeniorOS shipped no wrong code and never force-pushed main; Superpowers wrote wrong code three times (a refactor fixed only where a test pointed, a password-hash switch that locked out existing accounts). Every run, task and caveat (including which tasks were written alongside the changes they reward) is in evals/bench/, and you can rerun it with one command.
## Why SeniorOS exists
Coding agents can already generate a lot of code. The expensive failures usually happen around the code:
reading half the repository for a one-line change;
reading too little before touching auth, data, or infrastructure;
changing unrelated files because they looked “helpful”;
declaring success without running the project's real checks;
weakening tests instead of understanding the regression;
forgetting architectural decisions between sessions;
treating a button rename and a production migration with the same ritual.
SeniorOS treats these as engineering-system problems, not prompt-writing problems.
> The goal is not to make the model sound senior. The goal is to make the workflow behave like disciplined engineering.
## How it works
SeniorOS pushes agent work toward a risk-adaptive loop:
text
Goal Contract
Relevant Context
Risk Assessment
Right-Sized Execution
Proof
Review
Ship / Not Proven / Blocked
The important part is that not every task gets the same process.
| Task | SeniorOS behavior |
| Rename a button | Direct edit + proportionate verification |
| Add an API route | Light plan + relevant tests |
| Change authentication | Full context + security/risk review + proof |
| Production migration | Strict plan + rollback thinking + explicit boundaries |
| “Just make CI green” | Investigate root cause before weakening meaningful checks |
### The difference in one line
text
normal agent loop: request → generate → edit → "done"
SeniorOS loop: request → understand → assess → execute → prove → review → state what is known
SeniorOS prefers:
text
PROOF BASELINE: PASS
Residual risk: LOW
Skipped checks: none
instead of:
text
Everything looks good! 🚀
because optimism remains stubbornly absent from every serious test framework.
## Quick start
Requires Node.js 20 or newer. No clone needed: the CLI is published on npm as senioros, and its command is senior.
### 1. Install SeniorOS for your coding agent
Claude Code (recommended: the plugin adds the routing rules and the destructive-command guard):
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/joshsegatt-senioros/)
- Source
- github · https://github.com/joshsegatt/SeniorOS
- Browse by field
- Agent skills
- Traction
- 3 ★
- Listed by
- 4 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.