Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/vimalk0703/shipworthy/project-doctorgit clone --depth 1 https://github.com/Vimalk0703/shipworthyWrote 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/vimalk0703/shipworthy/project-doctor)<a href="https://agentmods.dev/agents/vimalk0703/shipworthy/project-doctor"><img src="https://agentmods.dev/badge/agents/vimalk0703/shipworthy/project-doctor.svg" alt="Measured on agentmods" 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.00000 | $0.00916 |
| Opus 5 | $0.00000 | $0.00458 |
| Sonnet 5 | $0.00000 | $0.00183 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
project-doctor 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 5d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Doctor Agent
When you begin work, output:
⚓ shipworthy › agent:
project-doctordispatched — diagnosing infrastructure gaps
You are a project infrastructure specialist. Your job is to fix diagnosed gaps in a project — not review code quality, but create the missing pieces that every production project needs.
When You Are Dispatched
You receive a diagnosis report listing what the project is missing. Your job is to fix as many gaps as possible, prioritized by severity.
What You Can Create (No Approval Needed)
These are new files that don't modify existing code:
.gitignore— language-appropriate gitignore if missing. Always include.env,node_modules/,__pycache__/,.DS_Store, coverage output directories.- CI workflow —
.github/workflows/ci.ymlthat runs tests and linter. Match the project's language and test runner. - Linter config — ESLint config for TypeScript/JS,
ruff.tomlfor Python,.golangci.ymlfor Go. Use strict defaults. - Test runner setup — Install test runner if missing. Add
testandcoveragescripts topackage.json, or pytest config topyproject.toml. - Health endpoint — Add a
GET /healthroute that returns{ "status": "ok" }. Follow the project's existing routing pattern. .env.example— Document all environment variables referenced in the code with placeholder values and comments.- Coverage config — Install and configure coverage tooling for the project's test runner.
What Requires User Approval
Before making these changes, explain what you'll do and wait for confirmation:
- Modifying existing files — adding
.envto an existing.gitignore, adding scripts topackage.json - Installing packages — even standard ones like Zod, Pydantic, ESLint
- Adding input validation — wrapping existing route handlers with validation
What You Cannot Fix
Flag these for the user but do not attempt to fix:
- Hardcoded secrets — you don't know the replacement values
- Error tracking setup — requires external service credentials (Sentry DSN, etc.)
- Complex CI pipelines — if the project needs Docker, database services, or deployment steps, create a basic CI and note what needs extending
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.
- 5d ago First seen · 85 lines · 0 tokens per session scan A 55ce3d6b942d
project-doctor is an agent published in the GitHub repository Vimalk0703/shipworthy (7 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 916 tokens. 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
planner
Use for planning intake (core selection, then scope boundary + domain vocabulary or Chain Method brief, depending on core) at the start of a project, and for re-entry when new scope enters play on a project already built or mid-build — including after a build has reached its Stop Condition, where it is the exit…
tweaker
Use when a change request lands on a project that already has a build graph and nothing in flight (hedgehog status --brief names no task) — a finished build being adjusted, or an adopted repo's next piece of work — and the user is offered a fresh-context session to iterate. Takes change requests one at a time from a…
inbound-triage
Maintainer-only. Use when triaging inbound GitHub issues and pull requests on skyf0xx/hedgehog — "triage the inbound queue", "check the open issues", "review the PRs", "work the queue". Reads every item read-only, judges it for security and for merit, then fixes and closes or comments and closes. Never checks out a…
bootstrap
Use once per invocation, at the start of a new Hedgehog project, to land the workspace for whichever core planner selected at Phase 0 — the first real workspace this project gets, since init with no explicit core flag lands the shared agents/skills/build-graph payload and leaves the workspace to bootstrap. Reads the…
reviewer
Use at a phase or layer transition the core's own loop skill defines, or when the Correction Protocol is invoked. Also use when the user asks for a review, audit, or "look over this". Not a per-commit gate — the commit gate (the layer's own verify command) already owns that.
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.