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 ddanntheman/GrantForge --skill grant-intakegit clone --depth 1 https://github.com/ddanntheman/GrantForgeWrote 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/ddanntheman/grantforge/grant-intake)<a href="https://agentmods.dev/skills/ddanntheman/grantforge/grant-intake"><img src="https://agentmods.dev/badge/skills/ddanntheman/grantforge/grant-intake.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.1 | $0.00086 | $0.00883 |
| Opus 5 | $0.00043 | $0.00441 |
| Sonnet 5 | $0.00017 | $0.00177 |
| Haiku 4.5 | $0.00009 | $0.00088 |
Grade A, and why
grant-intake 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 7d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grant Intake
Turn a funding announcement into a complete, testable specification of what the application must contain. Everything downstream (research, drafting, budget, review) works off the requirements matrix produced here.
Requires the .grantforge/ profile; if missing, run grant-setup first.
Step 1 — Acquire the full announcement
Accept an uploaded document (PDF/Word), a pasted excerpt, or a URL. If given a URL or partial text, fetch and read the complete announcement including all appendices — page limits and scoring rubrics often hide in attachments. For federal grants, check Grants.gov for the related documents package. Never proceed on a summary alone; ask for the full document if what was provided is clearly partial.
Step 2 — Create the grant workspace
Create .grantforge/grants/<funder>-<program>-<year>/ containing:
requirements.md # The requirements matrix (this skill)
source/ # The announcement and attachments
research/ # Populated by grant-research
drafts/ # Populated by grant-draft
final/ # Submission-ready outputs
Register the opportunity in tracker.md with status intake.
Step 3 — Build the requirements matrix
Extract into requirements.md, as tables:
Overview: funder, program name, CFDA/ALN if federal, total pool, award range, match/cost-share requirement, indirect rate rules, period of performance, deadline (date, time, time zone), submission mechanism (portal, email, Grants.gov) and any registration lead time it implies.
Eligibility: every eligibility criterion as a row with columns
Criterion | Our status | Evidence. Fill "Our status" from the org profile.
Anything unverifiable becomes a question for the user.
Narrative requirements: one row per required section with columns
Section | Prompt (verbatim) | Limit (pages/words/chars) | Points | Notes.
Copy the funder's prompts verbatim — drafting will answer exactly these.
Capture the scoring rubric weights if published; grant-review scores
against them.
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.
- 7d ago First seen · 92 lines · 86 tokens per session scan A f57e6081fa6f
grant-intake is a skill published in the GitHub repository ddanntheman/GrantForge (2 stars, last pushed 2mo ago), licensed MIT. It adds 86 tokens to every session and 883 once invoked, about $0.0004 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
inno-grant-proposal
A writing aid for preparing and improving research grant proposals for US and Chinese funding agencies.
Grant Writer
Craft compelling grant proposals that secure funding for nonprofits and research.
kami-deck
A lab-meeting deck on gut-microbiome links to sleep quality — the design, the results, the caveats, and the next experiment. Built as a decision-grade academic research deck for lab group, PI.
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.