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 NickCrew/Claude-Cortex --skill development-estimationgit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/development-estimation)<a href="https://agentmods.dev/skills/nickcrew/claude-cortex/development-estimation"><img src="https://agentmods.dev/badge/skills/nickcrew/claude-cortex/development-estimation.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.00032 | $0.00344 |
| Opus 5 | $0.00016 | $0.00172 |
| Sonnet 5 | $0.00006 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
development-estimation 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 4d 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.
What it actually says
Development Estimation
Overview
Create consistent, defensible estimates by breaking scope into components, identifying risks, and providing confidence intervals.
When to Use
- Estimating feature or project scope
- Providing effort or complexity estimates
- Delivering risk-aware breakdowns
Avoid when:
- The task is trivial or a rough gut-check is sufficient
- Requirements are unknown and need discovery first
Quick Reference
| Task | Load reference |
|---|---|
| Estimation workflow | skills/development-estimation/references/estimate.md |
Workflow
- Define scope and estimation type (time/effort/complexity).
- Load the estimation reference for structure.
- Break into components and dependencies.
- Add risks and confidence intervals.
- Deliver estimate with assumptions.
Output
- Estimate with breakdown and confidence interval
- Assumptions, risks, and validation notes
Common Mistakes
- Estimating without clear scope
- Ignoring risk and dependency factors
- Overstating precision beyond available data
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 56 lines · 32 tokens per session scan A e3341870d87c
development-estimation is a skill published in the GitHub repository NickCrew/Claude-Cortex (38 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 344 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
cad-reviewer-contract
Internal role contract, preloaded into every cad-reviewer rung agent. Not a user command.
cad-plan-checker-contract
Internal role contract, preloaded into every cad-plan-checker rung agent. Not a user command.
ideogram-ultra
Build Ideogram 4 (Ideogram Ultra) txt2img and img2img workflows with the local open-weights model, dual conditional/unconditional models with DualModelGuider, Qwen3-VL text encoder, and structured JSON ("compositional deconstruction") prompts for strong text rendering and layout control.
chief-revenue-officer
Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not…
storybook-mcp-integration
Reference for the Storybook MCP server itself (@storybook/addon-mcp): 6 tools across 3 toolsets (dev, docs, testing), availability detection, and per-agent toolset filtering. Use when setting up the server or calling these tools directly against components that already exist. For the end-to-end pipeline that turns a…
spring-security-jwt
Use when an application issues and validates its own first-party JWT access and refresh tokens, including authentication filters, password encoding, RBAC, and method security. For JWTs issued by Keycloak, Auth0, Okta, Cognito, or another authorization server, use oauth2-resource-server.