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 build-with-dhiraj/ai-workflow-framework-portability-kit --skill evaluating-skill-necessitygit clone --depth 1 https://github.com/build-with-dhiraj/ai-workflow-framework-portability-kitWrote 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/build-with-dhiraj/ai-workflow-framework-portability-kit/evaluating-skill-necessity)<a href="https://agentmods.dev/skills/build-with-dhiraj/ai-workflow-framework-portability-kit/evaluating-skill-necessity"><img src="https://agentmods.dev/badge/skills/build-with-dhiraj/ai-workflow-framework-portability-kit/evaluating-skill-necessity/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/build-with-dhiraj/ai-workflow-framework-portability-kit/evaluating-skill-necessity"><img src="https://agentmods.dev/badge/skills/build-with-dhiraj/ai-workflow-framework-portability-kit/evaluating-skill-necessity.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.00028 | $0.00401 |
| Opus 5.5 | $0.00011 | $0.00160 |
| Sonnet 5.5 | $0.00006 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
Evaluating Skill Necessity 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 1mo 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
Evaluating Skill Necessity
This skill serves as the Mandatory First Step before adding any new capability to the agent's library. It prevents skill bloat and ensures high-quality, non-redundant instructions.
The Necessity Protocol
Whenever a new skill is proposed, follow this 4-step analysis:
1. Problem Definition
- What specific, repeatable task does this skill address?
- Is it a "Fragile" task (requires exact commands) or a "Flexible" task (requires heuristics)?
2. Redundancy Audit (Internal)
- Does the agent's base system prompt or model capabilities already handle this optimally?
- Rule: Do not create a skill for "General Writing" or "Basic Coding" as these are core model strengths.
3. Redundancy Audit (Library)
- Search the existing
.agent/skills/directory for overlapping keywords. - Does an existing skill already provide the necessary context?
- Tip: If an existing skill covers 80% of the need, consider Updating that skill instead of creating a new one.
4. Value Proposition
- Does this skill provide Specific Scripts, Validated Workflow Checklists, or Design Tokens that aren't easily hallucinated or researched?
- Does it enforce a Mandatory Protocol (like TDD or B.L.A.S.T.)?
Decision Logic
- PROCEED (Needed): Unique operational value, specific technical constraints, or mandatory business protocols.
- REJECT (Redundant): General knowledge, already covered by standard model capabilities, or purely informational without actionable workflows.
Mandatory Invocation
This skill MUST be invoked as the primary skill during the PLANNING phase of any "New Skill" task.
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.
- 1mo ago First seen · 36 lines · 28 tokens per session scan A f5ed0eaca9b1
Evaluating Skill Necessity is a skill published in the GitHub repository build-with-dhiraj/ai-workflow-framework-portability-kit (5 stars, last pushed 21d ago), licensed MIT. It adds 28 tokens to every session and 401 once invoked, about $0.0001 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-09-21.
Other skills, from other repositories
codeql
Run CodeQL database creation and security queries, add data-extension models, or process CodeQL SARIF. Use when CodeQL is explicitly requested; use security-review for a broader manual security review.
sharp-edges
Identify error-prone APIs, dangerous configuration, and footgun designs that enable security mistakes. Use for API ergonomics, misuse resistance, secure defaults, or pit-of-success reviews; use code-review for general defects.
huggingface-vision-trainer
Train object-detection, image-classification, or SAM segmentation models on Hugging Face Jobs. Use for vision fine-tuning and evaluation; use huggingface-llm-trainer for language models.
code-quality
Agents should invoke this skill for code reviews, linting/formatting setup, maintainability checks, complexity concerns, warning cleanup, coding standards, or quality gates in Rust, TypeScript, Python, shell, and mixed repos.
code-reviewer
Review code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter. Use this skill when reviewing a small set of changes locally (such as unstaged diff), when dispatched as a…
differential-review
Performs security-focused differential review of code changes (PRs, commits, diffs). Adapts analysis depth to codebase size, uses git history for context, calculates blast radius, checks test coverage, and generates comprehensive markdown reports. Automatically detects and prevents security regressions.