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 travisjneuman/.claude --skill grant-proposal-buildergit clone --depth 1 https://github.com/travisjneuman/.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/travisjneuman/.claude/grant-proposal-builder)<a href="https://agentmods.dev/skills/travisjneuman/.claude/grant-proposal-builder"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/grant-proposal-builder/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/travisjneuman/.claude/grant-proposal-builder"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/grant-proposal-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00037 | $0.04672 |
| Opus 5 | $0.00018 | $0.02336 |
| Sonnet 5 | $0.00007 | $0.00934 |
| Haiku 4.5 | $0.00004 | $0.00467 |
Grade A, and why
grant-proposal-builder 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.
How it starts
The opening of the file, as written. The whole thing — 549 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grant Proposal Builder
Comprehensive frameworks for developing competitive grant proposals across government, foundation, corporate, and research funding contexts.
Grant Proposal Structure
Universal Proposal Sections
STANDARD STRUCTURE:
1. COVER PAGE / TITLE PAGE
- Project title (clear, compelling, concise)
- Applicant organization name and address
- Principal Investigator / Project Director
- Requested amount and project period
- Funder program name and deadline
2. EXECUTIVE SUMMARY / ABSTRACT (1 page)
- Problem statement (2-3 sentences)
- Proposed solution (2-3 sentences)
- Goals and expected outcomes (2-3 sentences)
- Budget summary (1 sentence)
- Organization qualifications (1-2 sentences)
3. STATEMENT OF NEED (2-4 pages)
- Problem definition with data
- Population affected
- Geographic scope
- Consequences of inaction
- Gap in current solutions
4. GOALS AND OBJECTIVES (1-2 pages)
- Goal statements (broad, long-term)
- SMART objectives (specific, measurable)
- Alignment with funder priorities
5. METHODOLOGY / PROJECT DESIGN (5-10 pages)
- Approach and activities
- Timeline and milestones
- Staffing and roles
- Partnerships and collaborations
- Innovation and evidence base
6. EVALUATION PLAN (2-4 pages)
- Process evaluation design
- Outcome evaluation design
- Data collection methods
- Analysis approach
- Reporting schedule
7. BUDGET AND BUDGET NARRATIVE (2-5 pages)
- Line-item budget
- Budget justification narrative
- Matching/cost-share (if required)
8. SUSTAINABILITY PLAN (1-2 pages)
- Post-grant funding strategy
- Institutional commitment
- Revenue diversification
9. ORGANIZATIONAL CAPACITY (1-2 pages)
- Mission and history
- Relevant experience
- Key staff qualifications
- Past performance
10. APPENDICES
- Letters of support
- Staff CVs/resumes
- Organizational chart
- Tax-exempt documentation
- Data tables and supplementary materials
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 · 549 lines · 37 tokens per session scan A a7f2ffab62d5
grant-proposal-builder is a skill published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 7d ago), licensed MIT. It adds 37 tokens to every session and 4,672 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
plan-review-architecture
Architecture-dimension reviewer for written plans. Use when running plan-review or directly when an architectural review is wanted. Activate for keywords like "architecture review", "data flow", "failure modes", "rollback", "edge cases", "test matrix". Scores 5 sub-dimensions 0-10, produces ranked fixes. Always cite…
plan-review-experience
Experience-dimension reviewer for written plans (UX + DX). Use when running plan-review or directly when an experience review is wanted. Activate for keywords like "UX review", "DX review", "experience review", "error states", "API ergonomics", "developer experience", "user states". Scores 5 sub-dimensions 0-10…
audit-dependencies
Use when investigating dependency bloat, security advisories, supply-chain risk, upgrade planning, or before adding a new third-party package. Activate for keywords like "deps", "dependencies", "package.json", "requirements.txt", "Cargo.toml", "audit", "CVE", "stale package", "do we use", "what depends on"…
code-review-loop
Use when opening a PR for review or when receiving review feedback. Activate for keywords like "code review", "PR review", "request review", "review feedback", "address comments", "reviewer said". Covers both ends of the loop: preparing a reviewable PR and acting on feedback rigorously. Always engage with every…
evidence-driven-debugging
Use during active debugging when you have a hypothesis to test or need to instrument a running system. Activate for keywords like "debug", "instrument", "log", "trace", "breakpoint", "what's happening at runtime", "production behavior". Pair to investigate-root-cause for the doing-it phase. Always record what you…
incremental-shipping
Use when implementing a non-trivial feature, migration, or refactor that would otherwise be a single large change. Activate for keywords like "feature flag", "incremental", "vertical slice", "migration", "rollout", "behind a flag", "ship small". Enforces vertical slicing, feature-flagged rollout, and refactor-with…