Borrowing it
Nothing to install: this file belongs to mysleekdesigns/crawlforge-mcp. 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/mysleekdesigns/crawlforge-mcp/main/.claude/skills/next-phase/SKILL.mdgit clone --depth 1 https://github.com/mysleekdesigns/crawlforge-mcpWrote 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/mysleekdesigns/crawlforge-mcp/next-phase)<a href="https://agentmods.dev/skills/mysleekdesigns/crawlforge-mcp/next-phase"><img src="https://agentmods.dev/badge/skills/mysleekdesigns/crawlforge-mcp/next-phase/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/mysleekdesigns/crawlforge-mcp/next-phase"><img src="https://agentmods.dev/badge/skills/mysleekdesigns/crawlforge-mcp/next-phase.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.00107 | $0.02996 |
| Opus 5.5 | $0.00043 | $0.01198 |
| Sonnet 5.5 | $0.00021 | $0.00599 |
| Haiku 4.5 | $0.00011 | $0.00300 |
Grade A, and why
next-phase 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 13d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/next-phase — Ship the next phase of the plan/ folder
You orchestrate exactly one phase of the remediation plan in plan/ from start to push, then stop. Repeated invocations walk the plan in order: Phase 0 → 1 → 2 → 3 → 4 → 5 → 6. You do not implement the work yourself — you delegate to specialized sub-agents in parallel and integrate their work.
The plan lives in plan/:
plan/README.md— index + sequencing + the phase table.plan/phase-0-dependency-currency.md…plan/phase-6-mcp-competitive.md— one file per phase.- Full failure detail for every finding:
docs/CODEBASE_AUDIT_2026-08.md.
Each phase file has a ## Checklist of - [ ] items and a ## Verification gate of - [ ] items. A code finding looks like:
- [ ] 🔴 **<title>** · CONFIRMED
- `src/utils/ssrfGuard.js:129`
- Failure: <concrete failure scenario>
- Fix: <the fix>
The `file:line` and Fix: sub-bullets are the contract you hand to the sub-agent — copy them verbatim, don't paraphrase.
Hard rules
- One phase per invocation. Detect the lowest-numbered incomplete phase, ship it, stop.
- Never amend. Always create a new commit.
- Never
--no-verify,--no-gpg-sign, or force-push. - Never
git add -A/git add .— stage files by name. - If the working tree is dirty before Step 1 (anything other than the plan files themselves), stop and report — don't sweep other work into the commit.
- If any verification step fails, stop before commit, leave the tree as-is, and report the failure with output.
- All sub-agent calls in Step 3 go out in a single message with multiple
Agenttool calls so they run in parallel. - Disjoint file ownership. No two parallel agents may edit the same file (they share the real working tree, not worktrees — concurrent edits to one file corrupt it).
server.jsand sharedsrc/utils/*are hotspots; give each hot file to a single agent. - In this environment,
git,npm install/update, and the test suites may fail under a restrictive sandbox (listen EPERM / write EPERM are artifacts, not real failures). If a step fails that way, re-run it with the sandbox disabled. Manualnode --testruns need--test-force-exitplaced before the file path (after it, the flag is silently ignored; a Playwright handle otherwise hangs the exit — see CLAUDE.md).npm run test:unitalready sets it.
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.
- 13d ago Changed · +2 lines · +2 tokens per session 808b50e88ff0
- 1mo ago First seen · 160 lines · 105 tokens per session scan A 92ebe4765cba
next-phase is a skill published in the GitHub repository mysleekdesigns/crawlforge-mcp (6 stars, last pushed 2d ago), licensed MIT. It adds 107 tokens to every session and 2,996 once invoked, about $0.0004 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 skills, from other repositories
healthcare-providers-enrich
Fills gaps in existing healthcare practitioner lists — adds missing phone numbers, credentials, specialties, contact info, education, reviews, and regulatory data. Triggers: "enrich my provider list", "fill in missing data", "add phone numbers to these doctors", "complete this practitioner database", "enrich CRM…
healthcare-providers-extract
Extracts structured practitioner data from healthcare practice websites. Returns names, credentials, specialties, contact info, and education for every provider on a practice's site. Use when user asks to extract, pull, or list doctors, providers, or staff from practice websites. Triggers: "extract doctors from"…
talent-sourcing
Finds qualified candidates for a role by searching LinkedIn, Indeed, GitHub, and other professional platforms using Nimble Web Search Agents. Accepts a job description, role title, or freeform request and returns a ranked candidate list with profiles, skills, and contact signals. Use this skill when the user wants to…
chatcrystal-debug-recall
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.
verify
Fact-check claims encountered during reading — dates, names, events, citations. Use when encountering historical facts or disputed claims.
megalinter-check
Collect MegaLinter lint errors for the current repository. Use when the user wants to know if the code passes linting, why the MegaLinter CI job fails, or before/after fixing lint errors. Two modes - watch a CI job (GitHub Actions, GitLab CI, Azure Pipelines, Bitbucket Pipelines) and parse its logs, or run MegaLinter…