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 paruff/uFawkesAI --skill effort-estimationgit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/paruff/ufawkesai/effort-estimation)<a href="https://agentmods.dev/skills/paruff/ufawkesai/effort-estimation"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/effort-estimation/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/paruff/ufawkesai/effort-estimation"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/effort-estimation.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.00027 | $0.00513 |
| Opus 5 | $0.00014 | $0.00257 |
| Sonnet 5 | $0.00005 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
effort-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 8d 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
Skill: Effort Estimation
Load trigger:
"load effort-estimation skill"> DORA: Cap 3 (AI-Accessible Internal Data) Token cost: Low
Purpose
Estimate complexity and effort for each task.
Responsibilities
- Estimate time to complete each task
- Estimate complexity (simple / moderate / complex)
- Identify high-risk tasks
- Identify long-pole tasks on the critical path
Inputs
tasks.json
Outputs
effort-estimates.json
Estimation Factors
Complexity Levels
| Level | Description | Typical Lines | Typical Time |
|---|---|---|---|
| Simple | Single file, clear pattern | < 100 | < 1 hour |
| Moderate | Multiple files, some decisions | 100–300 | 1–3 hours |
| Complex | Multiple systems, architectural decisions | 300–400 | 3–6 hours |
Risk Factors
- New technology or library usage → +1 complexity level
- Multiple integration points → +1 complexity level
- Security-sensitive code → flag for review
- No existing tests in area → flag for test generation
- External API dependency → flag for mock/stub
Long-Pole Detection
- Tasks on the critical path are flagged
- Tasks with most downstream dependencies are flagged
- Tasks requiring external approval are flagged
Output Format
{
"task_id": "TASK-001",
"title": "Task title",
"complexity": "simple | moderate | complex",
"estimated_lines": 150,
"estimated_hours": 2,
"risk_factors": ["multiple integration points"],
"is_long_pole": false,
"is_on_critical_path": true
}
Success Criteria
- Estimates are consistent and reasonable
- High-risk tasks identified
- Long-pole tasks identified
- No task estimated above 400 lines
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.
- 8d ago First seen · 80 lines · 27 tokens per session scan A 01b26fa565f9
effort-estimation is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 19d ago), licensed MIT. It adds 27 tokens to every session and 513 once invoked, about $0.0001 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
infrastructure-rules
Skill for the rules module — discovery, validation, scope, and private-sidecar symlink sync for the top-level rules/ directory (specifications include soft markdown guidelines and strong yaml/json formal constraints). Use when discovering rules (discoverrules), resolving a rule path (resolveruleroot), validating rule…
infrastructure-project
Skill for the project management infrastructure module providing multi-project discovery, structure validation, and metadata extraction. Use when discovering active projects, validating project directory structure, or extracting project configuration metadata.
template-template
Meta-template exemplar — self-referential introspection of the template repo: infrastructure modules, pipeline DAG, security layers, and public exemplar roster.
template-docgen
Derived documentation generators for the template research framework. Scripts that write to docs/generated/ and update in-place doc blocks.
construction-trades-supervisor
Use when a task needs the judgment of a Construction Trades Supervisor (foreman) — allocating a crew's daily task assignments against a labor-unit budget, deciding whether today's scope requires a formally designated OSHA competent person, arbitrating a trade-sequencing conflict between crews needing the same physical…
architectural-engineering-manager
Use when a task needs the judgment of an Architecture/Engineering firm or department manager — pricing a project fee (lump sum vs. hourly vs. % of construction cost), staffing a project against backlog, evaluating scope creep on a fixed-fee job, managing professional liability exposure, or deciding whether to pursue a…