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/Yorha9e/moamcpWrote 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/yorha9e/moamcp/tip-new)<a href="https://agentmods.dev/commands/yorha9e/moamcp/tip-new"><img src="https://agentmods.dev/badge/commands/yorha9e/moamcp/tip-new/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/commands/yorha9e/moamcp/tip-new"><img src="https://agentmods.dev/badge/commands/yorha9e/moamcp/tip-new.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.00023 | $0.00287 |
| Opus 5.5 | $0.00009 | $0.00115 |
| Sonnet 5.5 | $0.00005 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
tip-new 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
从当前讨论整理并新建一个项目级 Tip。执行步骤：
- 取系统提示中当前 Working Directory 的绝对路径作为
workspace（moamcp 进程的 cwd 是插件根，不是项目根，不可用作 workspace）。 - 根据
$ARGUMENTS的描述（缺省为当前讨论内容）整理草案：title（简短）、summary（几句话说明目标与预期价值）、context（足够恢复讨论的大概背景，4–8 KiB 以内，不复制完整对话）、status（默认captured）、module/tags（如有）、documentRefs/sourceRefs/relatedTipIds（如有；文档路径用相对项目根）。 - 把草案展示给用户确认，明确告知"保存为项目级 Tip，跨 Session 可见，可后续查阅/归档"。
- 用户确认后调用
moa_tip_create（传workspace与完整字段）保存；未经用户确认绝不静默保存。普通临时对话、一次性指令不得写入 Tip。
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 · 11 lines · 23 tokens per session scan A ca343c54242e
tip-new is a command published in the GitHub repository Yorha9e/moamcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 287 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.