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 skills add Vimalk0703/shipworthy --skill project-diagnosisgit 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/skills/vimalk0703/shipworthy/project-diagnosis)<a href="https://agentmods.dev/skills/vimalk0703/shipworthy/project-diagnosis"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/project-diagnosis/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/vimalk0703/shipworthy/project-diagnosis"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/project-diagnosis.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.00063 | $0.01503 |
| Opus 5 | $0.00032 | $0.00751 |
| Sonnet 5 | $0.00013 | $0.00301 |
| Haiku 4.5 | $0.00006 | $0.00150 |
Grade A, and why
project-diagnosis 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 9d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Diagnosis
Purpose
Most projects don't fail because their code is bad — they fail because things are missing. No tests, no CI, no input validation, no error handling, no logging. This skill systematically checks for what's absent and surfaces concrete, actionable findings.
This is NOT a code review. The /audit command reviews code quality. This skill checks project infrastructure completeness.
Diagnosis Checklist
Run through each category. For each check, record: present (pass), absent (finding), or not applicable (skip).
1. Testing Infrastructure
| Check | How to Verify | Severity if Missing |
|---|---|---|
| Test directory exists | Look for tests/, __tests__/, test/, spec/, or test file patterns (*.test.*, *.spec.*, test_*.py, *_test.go) |
High |
| Test runner configured | package.json has test script, OR pytest.ini/pyproject.toml has pytest config, OR go test works |
High |
| Coverage configured | @vitest/coverage-v8, pytest-cov, go test -cover, or equivalent is installed |
Medium |
| At least 1 test exists | At least one test file has actual test cases (not just empty files) | High |
2. CI/CD Configuration
| Check | How to Verify | Severity if Missing |
|---|---|---|
| CI config exists | .github/workflows/, .gitlab-ci.yml, .circleci/config.yml, Jenkinsfile, .travis.yml |
Medium |
| CI runs tests | CI config includes a test step | Medium |
| CI runs linter | CI config includes a lint step | Low |
3. Security Basics
| Check | How to Verify | Severity if Missing |
|---|---|---|
.env in .gitignore |
.gitignore exists and contains .env |
Critical |
| No hardcoded secrets | Quick scan for patterns: password = ", apiKey = ", secret = ", token = " in source files |
Critical |
| Input validation present | If API routes exist, check for Zod/Pydantic/validator imports near route handlers | High |
| Dependency audit clean | npm audit / pip audit / go vuln shows no critical vulnerabilities |
Medium |
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.
- 9d ago First seen · 115 lines · 63 tokens per session scan A 166f1a301340
project-diagnosis is a skill published in the GitHub repository Vimalk0703/shipworthy (7 stars, last pushed 5mo ago), licensed MIT. It adds 63 tokens to every session and 1,503 once invoked, about $0.0003 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
dare-refine
Analisa complexidade de uma task DARE e, quando alta, quebra em sub-tasks menores. Use após gerar o DAG (para tasks HIGH/CRITICAL), quando o dev pedir refinamento manual, ou quando o escopo mudou e uma task ficou grande. Combina heurística determinística (CLI) com decisão semântica do agente.
dare-dag
Mostra o DAG estático de tasks (DARE/dare-dag.yaml): ranks, dependências e caminho crítico. Use dare dag viz para exportar o diagrama. Mapeia o CLI dare dag.
dare-graph
Consulta e visualiza o grafo de conhecimento do projeto (tasks, arquivos, schemas, endpoints, componentes, entidades e suas relações). Mapeia o CLI dare graph.
setup-engine
Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
create-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
team-qa
Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.