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 skills/e1024kb/wise-claude/wise-estimationnpx skills add e1024kb/wise-claude --skill wise-estimationgit clone --depth 1 https://github.com/e1024kb/wise-claudeWrote 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/e1024kb/wise-claude/wise-estimation)<a href="https://agentmods.dev/skills/e1024kb/wise-claude/wise-estimation"><img src="https://agentmods.dev/badge/skills/e1024kb/wise-claude/wise-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 | $0.00128 | $0.01288 |
| Opus 5 | $0.00064 | $0.00644 |
| Sonnet 5 | $0.00026 | $0.00258 |
| Haiku 4.5 | $0.00013 | $0.00129 |
Grade A, and why
wise-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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Story-Point Estimation
Canonical story-point (SP) scale for sizing Jira tickets. Applies to every team (frontend, backend, mobile, platform) — using the same units so cross-team planning works.
This is a reference doc, not a procedure. When the user is planning a ticket or breaking work into tasks, consult this scale to pick a value; when the user asks "is this a 3 or a 5?", walk the complexity/scope/time axes below to decide.
The scale
Fibonacci, with a 0.5 minimum for truly trivial work.
| SP | Complexity | Typical scope | Calendar time |
|---|---|---|---|
| 0.5 | Trivial, mechanical | Single file, one obvious change (copy tweak, constant rename, one-line config) | ~half day |
| 1 | Simple, well-understood | 1–2 files, clear requirements, pattern already exists | ~1 day |
| 2 | Moderate | 3–5 files, some decisions to make, one or two unknowns | ~2 days |
| 3 | Complex | Multiple components, non-trivial logic, meaningful test surface | ~3 days |
| 5 | Large feature | Architecture decisions, several components, full test coverage | ~1 week |
| 8 | Epic-level | Multiple sub-tasks, crosses file/module boundaries, touches API + UI | ~2 weeks |
| 13 | Major feature with unknowns | Research needed, spec not fully baked, architecture open | ~3 weeks+ |
How to pick a number
Size against three axes. The estimate is the HIGHEST of the three, not the average — an unfamiliar-tech ticket with one file is still not a 1.
- Scope — how many files, components, or systems change?
- Complexity — how much decision-making, algorithmic work, or cross-cutting coordination is involved?
- Uncertainty — how much of the work is genuinely understood up-front vs. will-need-to-figure-it-out-as-we-go?
Examples:
- Change a button colour across one component + its story → 0.5 (low on all three).
- Add a new field to an existing form, with validation, backend wiring, and tests → 2 (scope drives it).
- Rewrite a contested caching layer with existing patterns → 3 (complexity drives it).
- Integrate a third-party SDK we've never used → 5 minimum (uncertainty drives it, even if the file count is small).
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 · 114 lines · 128 tokens per session scan A e40d6b3084b7
wise-estimation is a skill published in the GitHub repository e1024kb/wise-claude (4 stars, last pushed 9d ago), licensed MIT. It adds 128 tokens to every session and 1,288 once invoked, about $0.0006 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
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
codex-test-gen
Generate unit tests for specified functions using Codex MCP.
brand-docx
Brand-aware Word engine. Use to (1) EXTRACT a company's brand from a Word template into a reusable "Brand Profile", (2) COMPREHEND the template with the model (optional), (3) VERIFY it, (4) GENERATE new on-brand .docx documents FROM a saved profile. Trigger on "extract our brand", "learn/match this template", "use our…
extract-resume
Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.