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.
git clone --depth 1 https://github.com/hanhuark/mechanical-engineering-research-skillWrote 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/commands/hanhuark/mechanical-engineering-research-skill/me-proposal)<a href="https://agentmods.dev/commands/hanhuark/mechanical-engineering-research-skill/me-proposal"><img src="https://agentmods.dev/badge/commands/hanhuark/mechanical-engineering-research-skill/me-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.00032 | $0.00267 |
| Opus 5 | $0.00016 | $0.00133 |
| Sonnet 5 | $0.00006 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
me-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.
What it actually says
Thermal-Fluid Proposal Development
Use mechanical-engineering-research to develop, revise, or review a proposal for thermal-fluid or mechanical-engineering research.
Workflow:
- Start from the solicitation, review criteria, page limits, required sections, and collaborator-document requirements.
- Build the first-page logic: importance, unresolved barrier, proposed advance, feasibility, and expected impact.
- Organize the narrative around one overall goal and two to four objectives, aims, or thrusts.
- For each thrust, connect hypothesis, tasks, methods, preliminary results, expected outcomes, metrics, risks, and alternatives.
- Use figures as reviewer shortcuts: overview, mechanism, testbed, preliminary data, workflow, milestone table, and collaboration map.
- Revise against reviewer-friction points: vague central hypothesis, parallel rather than integrated methods, unmeasurable milestones, weak risk mitigation, and unclear partner roles.
Expected output:
- proposal logic map
- section-by-section outline or revised narrative
- figure and caption plan
- preliminary-results integration plan
- milestone and risk table
- review-criteria alignment checklist
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 · 26 lines · 32 tokens per session scan A a8e26ca97ffb
me-proposal is a command published in the GitHub repository hanhuark/mechanical-engineering-research-skill (16 stars, last pushed 10d ago), licensed MIT. It adds 32 tokens to every session and 267 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 commands, from other repositories
security-review
Complete a security review of the pending changes on the current branch.
launch-rhinos
Launch N parallel Rhino MCP sessions via the router and fan out one agent per Rhino.
launch-rhino
Launch a single Rhino MCP session via the router.
build
Build a feature using the adversarial review loop. Default tier: parent works end-to-end, zero subagent spawns. --strict tier adds critic + external review.
check-pr
Check the current branch's PR for external review feedback, fix errors and warnings, run a final external review, and push.
snapshot
Capture the current Rhino viewport and describe what's on screen.