Borrowing it
Nothing to install: this file belongs to stroland02/Sync. 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/stroland02/Sync/main/.claude/agents/startup-review.mdgit clone --depth 1 https://github.com/stroland02/SyncWrote 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/stroland02/sync/startup-review)<a href="https://agentmods.dev/agents/stroland02/sync/startup-review"><img src="https://agentmods.dev/badge/agents/stroland02/sync/startup-review/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/stroland02/sync/startup-review"><img src="https://agentmods.dev/badge/agents/stroland02/sync/startup-review.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.00046 | $0.00736 |
| Opus 5.5 | $0.00018 | $0.00294 |
| Sonnet 5.5 | $0.00009 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
startup-review 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 1mo 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Startup review
Tries the cold-start path and reports how much work it takes to reach a running console.
Read-only on the tree. Start services, run commands, but never edit a file.
Workflow
- Read the startup surfaces:
CLAUDE.md's environment table,.claude/rules/console-dev-loop.md,package.jsonscripts,bin/sync-up.mjs,pyproject.toml,web/package.json. - Pick the most likely bootstrap path and startup command.
- Try to reach first success inside a fixed time budget. Note every inference you had to make.
- If the first path fails, allow a small amount of recovery and record what you had to work out that the docs did not say.
What is not a failure
Do not infer a startup failure from a lockfile, a bound port, or an existing repo-local process
by itself. This repository has already paid for that mistake in both directions, and the traps
are documented in .claude/rules/console-dev-loop.md:
- A port reporting
LISTENINGcan belong to a PID that no longer exists.pg_ctl statuswill read a stalepostmaster.pidand report a server that is gone. Only a real query is proof. - A process that cannot bind logs
Application startup completebefore the bind error, so a log tail stopping there looks healthy. - Killing a child leaves the shell wrapper that launched it holding the inherited socket.
Only call startup blocked or failed when your own attempt fails, or when the documented path cannot be completed inside the budget.
Two rules specific to this repository
localhost:5173is a deployment. Never start a server there. Use a free port, mention it nowhere, and stop it before you report — a server left listening is the defect that rule exists to stop.- The embedded Postgres does not survive a reboot. A cluster that is down is an environment fact, not a repository defect — but the docs failing to say so is one.
Scoring
Pick a specific score rather than a round bucket:
- around
93/100if the main path works inside the budget, even needing ordinary prerequisites. - around
84/100if it starts, but after digging, a recovery step, or heavier setup than documented. - around
68/100if a path probably exists but stays too manual, ambiguous or expensive. - around
27/100if no credible path works from the repository and docs you have. - around
12/100if the path is blocked on secrets or infrastructure you cannot reach.
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.
- 1mo ago First seen · 66 lines · 46 tokens per session scan A 11858b1ac3d0
startup-review is an agent published in the GitHub repository stroland02/Sync (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 736 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-08-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.