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 LigphiDonk/Oh-my--paper --skill inno-grant-proposalgit clone --depth 1 https://github.com/LigphiDonk/Oh-my--paperWrote 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/ligphidonk/oh-my--paper/inno-grant-proposal)<a href="https://agentmods.dev/skills/ligphidonk/oh-my--paper/inno-grant-proposal"><img src="https://agentmods.dev/badge/skills/ligphidonk/oh-my--paper/inno-grant-proposal/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/ligphidonk/oh-my--paper/inno-grant-proposal"><img src="https://agentmods.dev/badge/skills/ligphidonk/oh-my--paper/inno-grant-proposal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 481 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- medium Excessive Agency · line 173 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00046 | $0.09403 |
| Opus 5 | $0.00023 | $0.04702 |
| Sonnet 5 | $0.00009 | $0.01881 |
| Haiku 4.5 | $0.00005 | $0.00940 |
Grade A, and why
inno-grant-proposal 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 12d 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 — 971 lines — stays where its author put it; the contents beside it link to each section on GitHub.
inno-grant-proposal
Canonical Summary
Help professors and researchers write, revise, adapt, and polish grant proposals for US agencies (NSF, NIH, DOE, DARPA, NASA) and Chinese agencies (NSFC 国自然). Use this skill whenever the user mentions grants, proposals, funding application...
Trigger Rules
Use this skill when the user request matches its research workflow scope. Prefer the bundled resources instead of recreating templates or reference material. Keep outputs traceable to project files, citations, scripts, or upstream evidence.
Resource Use Rules
- Read from
references/only when the current task needs the extra detail. - Treat
scripts/as optional helpers. Run them only when their dependencies are available, keep outputs in the project workspace, and explain a manual fallback if execution is blocked. - Reuse files under
templates/instead of recreating equivalent structure from scratch when the user asks for the matching deliverable.
Execution Contract
- Resolve every relative path from this skill directory first.
- Prefer inspection before mutation when invoking bundled scripts.
- If a required runtime, CLI, credential, or API is unavailable, explain the blocker and continue with the best manual fallback instead of silently skipping the step.
- Do not write generated artifacts back into the skill directory; save them inside the active project workspace.
Upstream Instructions
Grant Proposal Skill
Core Philosophy
Three principles govern every interaction:
- Grant applications are arguments, not requests. Every section must advance a persuasive case. The narrative arc is: problem is important, you are the right person, your approach will work, the investment is justified.
- Write like a domain expert, not a template filler. Generic language kills proposals. Every sentence must reflect deep knowledge of the specific field.
- Grant is not Paper. A paper reports results; a grant sells a future. Different narrative arc, different evidence standards, different rhetoric.
What ships with it
28 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 231 B
- config.yaml 3.6 KB
- CREDITS.md 4.5 KB
- evals/evals.json 3.8 KB
- references/cn/nsfc_guide.md 33 KB
- references/common/ai_flavor_checklist.md 2.1 KB
- references/common/common_mistakes.md 27 KB
- references/common/post_submission.md 735 B
- references/common/resubmission.md 20 KB
- references/common/reviewer_personas.md 18 KB
- references/rubrics/nih_rubric.json 14 KB
- references/rubrics/nsf_rubric.json 11 KB
- references/rubrics/nsfc_rubric.json 15 KB
- references/us/darpa_guide.md 14 KB
- references/us/doe_guide.md 12 KB
- references/us/nasa_guide.md 14 KB
- references/us/nih_guide.md 26 KB
- references/us/nsf_guide.md 23 KB
- scripts/compliance_check.py 17 KB runs code
- scripts/validate_citations.py 15 KB runs code
- scripts/validate_length.py 12 KB runs code
- templates/cn/nsfc_abstract_5sentence.md 4.3 KB
- templates/cn/nsfc_justification.md 5.2 KB
- templates/cn/nsfc_research_content.md 8.9 KB
- templates/cn/nsfc_research_foundation.md 4.2 KB
- templates/us/budget_justification.md 8.0 KB
- templates/us/nih_specific_aims.md 6.3 KB
- templates/us/nsf_project_summary.md 2.1 KB
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.
- 12d ago First seen · 971 lines · 46 tokens per session scan A c32959c4dd10
inno-grant-proposal is a skill published in the GitHub repository LigphiDonk/Oh-my--paper (722 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 9,403 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-08-30.
Other skills, from other repositories
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.
html-ppt-zhangzara-monochrome
A grant proposal on CRISPR base-editing for sickle-cell disease — the hypothesis, the approach, the milestones, and the risk. Built as a decision-grade academic research deck for grant review committee.
Paper Writing Skills Index
Routing and workflow skill family for paper-writing tasks. Covers manuscript drafting, journal and conference papers, grant proposals, lab reports, group-meeting reports, talks, workshop notes, reviewer rebuttals, academic HTML/PDF/LaTeX output with editable-block contracts, citation grounding, evidence checking, and…
grant-setup
First-run setup for GrantForge. This skill should be used when the user says "set up GrantForge", "set up my organization", "enter my company information", "create my org profile", or when any other GrantForge skill runs and no .grantforge/ profile exists yet. Conducts a structured interview about the organization and…
grant-intake
Parse a grant opportunity into a structured requirements matrix and issue a go/no-go recommendation. This skill should be used when the user says "here's a grant we want to apply for", "respond to this RFP", "parse this NOFO", "we're applying for X grant", "are we eligible for this?", or uploads a funding…
grant-draft
Write the grant application narrative. This skill should be used when the user says "draft the application", "write the need statement", "draft the project narrative", "write our response to section X", or after research is complete for a grant in the pipeline. Produces section drafts that answer the funder's prompts…