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-trackergit 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-tracker)<a href="https://agentmods.dev/skills/ddanntheman/grantforge/grant-tracker"><img src="https://agentmods.dev/badge/skills/ddanntheman/grantforge/grant-tracker/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/ddanntheman/grantforge/grant-tracker"><img src="https://agentmods.dev/badge/skills/ddanntheman/grantforge/grant-tracker.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.00069 | $0.00505 |
| Opus 5.5 | $0.00028 | $0.00202 |
| Sonnet 5.5 | $0.00014 | $0.00101 |
| Haiku 4.5 | $0.00007 | $0.00051 |
Grade A, and why
grant-tracker 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
Grant Tracker
Keep .grantforge/tracker.md as the single source of truth for every
opportunity across its life. The tracker compounds: every closed
application feeds lessons and reusable language back into the profile.
Tracker format
A markdown table, one row per opportunity:
Funder | Program | Amount requested | Deadline | Status | Workspace folder | Next action | Owner | Notes
Statuses: watching → intake → preparing → ready to submit →
submitted → awarded / declined / withdrawn. Keep closed items in
a separate "Closed" table at the bottom with outcome and amount.
Behaviors
Status report. When asked about the pipeline, read the tracker and
report: items due in the next 30 days (sorted by deadline, with days
remaining), items stuck without movement, and totals (requested vs.
awarded year-to-date, win rate on decided applications). Flag any
preparing item whose deadline is inside the review buffer (5 days) and
has not been through grant-review.
Updates. On any status change, update the row, date-stamp it in Notes, and set the next action. Other GrantForge skills call this behavior when they move an application forward.
On submission. Record submission date, confirmation number, and expected decision date if known. Set next action to the follow-up.
On decision. Record award or decline, amount, and any reviewer
feedback the funder provided — save feedback verbatim into the grant's
workspace folder. Then run the harvest: identify the strongest sections of
the application (or, on a decline, what reviewer feedback says to fix) and
offer to update profile/boilerplate/ and the org profile's track-record
section. Wins get added to the track record immediately.
Recurring check. Offer to schedule a weekly pipeline check that reports upcoming deadlines and stalled items.
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 · 52 lines · 69 tokens per session scan A 06f31c41dac9
grant-tracker is a skill published in the GitHub repository ddanntheman/GrantForge (2 stars, last pushed 3mo ago), licensed MIT. It adds 69 tokens to every session and 505 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
workspace
Multi-repo campaign coordinator. Same lifecycle as fleet -- scope claims, discovery relay, wave-based execution -- but the unit of work is a repo, not a file. Coordinates campaigns across repositories with shared context.
decision-map
Turn a loose idea into a git-tracked, session-resumable map of typed investigation tickets, then drive them to resolution one at a time. The planning-loop engine for work that is still being figured out — too fuzzy for a campaign, too big for a single intake item. Resolved tickets graduate into .planning/intake/ for…
unharness
Safely leave Citadel using the active adoption receipt. Produces a no-write, reviewable plan, preserves a portable archive, removes only exact owned material, and reports modified or externally registered surfaces as retained or unknown. Legacy installs must be imported before exact leave is claimed.
grants
Use when pursuing non-dilutive public or foundation funding — money you neither repay nor give equity for: finding a fit call, go/no-go, registration (UEI/PIC/BDNS), or writing the rubric-scored application, logic model, budget justification, or LOI. NOT an equity round (that is fundraising), NOT a paying-customer SOW…
project
A single starting point for setting up an AI-assisted project in Claude Cowork. It asks questions about the work, reviews available add-ons, and creates project instructions, custom agents, and connected workflows.