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 frankaging/lite-research-agents --skill research-proposalgit clone --depth 1 https://github.com/frankaging/lite-research-agentsWrote 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/frankaging/lite-research-agents/research-proposal)<a href="https://agentmods.dev/skills/frankaging/lite-research-agents/research-proposal"><img src="https://agentmods.dev/badge/skills/frankaging/lite-research-agents/research-proposal.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.00014 | $0.00397 |
| Opus 5 | $0.00007 | $0.00198 |
| Sonnet 5 | $0.00003 | $0.00079 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
research-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- research-proposal — 100% identical, 0 lines differ
What it actually says
Research Proposal
A research proposal is a structured 2-page document. Every section must be present. Be concrete — vague claims are not acceptable.
Sections
1. Problem Statement and Task Definition
What does the system do? What is its input and output? What real-world problem does it solve? Scope must be neither too narrow nor too broad.
2. Input / Output Behavior
Concrete examples of inputs and outputs. Describe what the input and output variables look like and how they interact. Reference the actual data being used — do not describe hypothetical data.
3. Evaluation Metric
How will success be measured? Why is this metric the right one for this problem? A reasonably sized dataset of example input-output pairs must be identified — either from an existing source or collected from scratch.
4. Related Works
What existing research and projects are relevant? How does the proposed work differ? Reference specific papers and systems, not general fields.
5. Baseline and Oracle
- Baseline: a simple, easy-to-implement approach that gives a lower bound on expected performance
- Oracle: an upper bound — what would near-perfect performance look like?
- Neither needs to be implemented for the proposal, but both must be clearly described. If the gap between baseline and oracle is too small, the task is probably not well-chosen.
6. Methodology and Challenges
How will the problem be approached? Why does this method fit? What are the key challenges? What algorithms or models are appropriate, and what are the tradeoffs between accuracy and efficiency?
Requirements
- 2 pages maximum
- Every section must be present — do not skip or merge sections
- Concrete over vague in every section
- Related works must cite specific papers, not just name fields
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 · 43 lines · 14 tokens per session scan A 11f73e883032
research-proposal is a skill published in the GitHub repository frankaging/lite-research-agents (3 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 397 once invoked, about $0.0001 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
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
paid-ads-linkedin
Audit, diagnose, plan, and safely operate connected LinkedIn Ads accounts through the NotFair MCP, with an export-based fallback. Use for LinkedIn advertising, sponsored content, lead-generation forms, job-title or company targeting, campaign groups, creatives, conversions, lead quality, budgets, bids, or approved…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…
paid-ads-guide
Explain NotFair's paid-ads skills, installation, platform boundaries, account connections, and current product capabilities. Use for questions about how NotFair works, what it supports, how to install or connect it, plans or limits, or paid-media troubleshooting that is not an account-performance request.
arbor-agent-ideate
Strict IDEATE-stage skill for Arbor. Use immediately after TreeView(format="constraints") when drafting Idea Tree nodes, enforcing the ideadrafting and firstprinciplesprobe behavior, depth-aware idea levels, four-line TreeAddNode hypotheses, conflict checks, and self-filtering against shallow tweaks.