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 jezweb/claude-skills --skill award-applicationgit clone --depth 1 https://github.com/jezweb/claude-skillsWrote 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/jezweb/claude-skills/award-application)<a href="https://agentmods.dev/skills/jezweb/claude-skills/award-application"><img src="https://agentmods.dev/badge/skills/jezweb/claude-skills/award-application/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/jezweb/claude-skills/award-application"><img src="https://agentmods.dev/badge/skills/jezweb/claude-skills/award-application.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector pass
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.00062 | $0.01890 |
| Opus 5 | $0.00031 | $0.00945 |
| Sonnet 5 | $0.00012 | $0.00378 |
| Haiku 4.5 | $0.00006 | $0.00189 |
Grade A, and why
award-application 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 6d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Award Application Writer
Produces award submissions and grant applications that address every criterion with quantified evidence. The goal is a document where every paragraph earns points on the scorecard.
Process
Step 1: Gather the brief
Ask the user for:
- Award/grant name and organiser
- Selection criteria (the exact list, verbatim if possible)
- Word limits (per criterion and/or total)
- Judging rubric or weighting (if publicly available)
- Category entered (if multiple categories exist)
- Whether this is a first submission or a resubmission
- Any specific achievements, metrics, or stories they want included
If the user has a URL for the award, fetch the criteria page. Many awards publish judging guides or past winner profiles — these are gold for understanding what evaluators value.
Step 2: Map achievements to criteria
Create a working table before writing anything:
| Criterion | Key achievement | Evidence/metric | Story or example |
|---|---|---|---|
| Innovation | AI workflow automation | Report time: 3 days to 4 hours | Staff training program, 12 people |
| Growth | Revenue increase | 40% YoY, $X to $Y | New service line launched Q2 |
| Community | Pro bono program | 200 hours, 15 local orgs | Bushfire recovery site builds |
Every criterion must have at least one entry. A blank row means a missing section in the submission — and missing sections lose marks or trigger automatic rejection.
If the user cannot provide evidence for a criterion, flag it explicitly. Better to know the gap now than to submit vague filler.
Step 3: Write the submission
Address criteria in the exact order they appear on the application form. Judges often score sequentially — don't make them hunt for your answer to criterion 3 buried in the criterion 1 section.
For each criterion, use the STAR structure:
- Situation: Brief context (1-2 sentences). What was the starting point or challenge?
- Task: What needed to happen? What was the objective?
- Action: What specifically did you/the business do? Be concrete.
- Result: What changed? Quantify the outcome.
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.
- 6d ago First seen · 164 lines · 62 tokens per session scan A 09a148773339
award-application is a skill published in the GitHub repository jezweb/claude-skills (1,000 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 1,890 once invoked, about $0.0003 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
ensemble-solving
Generate multiple diverse solutions in parallel and select the best. Use for architecture decisions, code generation with multiple valid approaches, or creative tasks where exploring alternatives improves quality.
code-execution
Execute Python code locally with marketplace API access for 90%+ token savings on bulk operations. Activates when user requests bulk operations (10+ files), complex multi-step workflows, iterative processing, or mentions efficiency/performance.
code-refactor
Perform bulk code refactoring operations like renaming variables/functions across files, replacing patterns, and updating API calls. Use when users request renaming identifiers, replacing deprecated code patterns, updating method calls, or making consistent changes across multiple locations.
code-transfer
Transfer code between files with line-based precision. Use when users request copying code from one location to another, moving functions or classes between files, extracting code blocks, or inserting code at specific line numbers.
feature-planning
Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.
review-implementing
Process and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implement suggestions from reviews.