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 EvoClaw/amplify --skill using-amplifygit clone --depth 1 https://github.com/EvoClaw/amplifyWrote 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/evoclaw/amplify/using-amplify)<a href="https://agentmods.dev/skills/evoclaw/amplify/using-amplify"><img src="https://agentmods.dev/badge/skills/evoclaw/amplify/using-amplify/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/evoclaw/amplify/using-amplify"><img src="https://agentmods.dev/badge/skills/evoclaw/amplify/using-amplify.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.00031 | $0.04005 |
| Opus 5.5 | $0.00012 | $0.01602 |
| Sonnet 5.5 | $0.00006 | $0.00801 |
| Haiku 4.5 | $0.00003 | $0.00400 |
Grade A, and why
using-amplify 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.
How it starts
The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
This is not negotiable. This is not optional. You cannot rationalize your way out of this.
ABSOLUTE RULE #1: ONE PHASE PER TURN
- Present the phase deliverables and/or gate checklist to the user
- END YOUR RESPONSE AND WAIT FOR THE USER TO REPLY
- Only proceed to the next phase AFTER the user explicitly approves
THIS IS THE SINGLE MOST IMPORTANT RULE IN THE ENTIRE SYSTEM.
Violating this rule — even once — collapses the entire research workflow into a shallow one-shot demo. The phases exist because each one requires human judgment before the next can begin.
What "end your response" means
- After Phase 0: present
research-anchor.yamlsummary → STOP. Wait for user. - After Phase 1 + G1: present G1 checklist → STOP. Wait for user.
- After Phase 2: present feasibility assessment → STOP. Wait for user.
- After Phase 3 + G2: present frozen plan → STOP. Wait for user.
- After G3: present readiness check → STOP. Wait for user.
- After Phase 4a: present exploration report + options (proceed / local adjustment / focused re-discussion / return to Phase 3 / return to Phase 2) → STOP. Wait for user decision. Most common outcome is local adjustment, not full phase reset.
- After Phase 4b: present results summary → STOP. Ask: "Are results sufficient? Shall I proceed to results integration?"
- After Phase 5 + G4: present content outline → STOP. Ask: "Shall I proceed to paper writing?"
- During Phase 6: present EACH SECTION individually → STOP. Wait for user feedback on that section.
What counts as user approval
- Explicit: "approved", "yes", "proceed", "looks good, go ahead", "继续", "可以"
- NOT approval: silence, no response, "ok" (ambiguous), or your own judgment that "it looks fine"
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 · 272 lines · 31 tokens per session scan A bb9f0c096e06
using-amplify is a skill published in the GitHub repository EvoClaw/amplify (11 stars, last pushed 7mo ago), licensed MIT. It adds 31 tokens to every session and 4,005 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-30.
Other skills, from other repositories
make_plan
For external plan request scenarios, guides the Agent to request a clear, actionable, step-by-step plan from a stronger Agent via listagents and chatwithagent, emphasizing that the plan is executed by the requester, not by the consulted Agent.
gpt-image-2
A skill for generating or editing images with GPT Image 2 across local, host-provided, or advisory setups.
motion-showreel
A code-based workflow for making short videos built from animated graphics, text, logos, or interface elements. It produces MP4 video and editable source code rather than filming or editing existing footage.
new
Create a new project to start development quickly.
oss-upload
Upload local files to Tencent COS (oss.1024code.com CDN) using coscli. Use when user wants to upload a file to CDN/OSS, or deploy static assets.
officecli-word-form
Use this skill to create fillable Word forms (.docx) with real Content Controls (SDT) + legacy FormField checkboxes + MERGEFIELD mail-merge placeholders + document protection. Trigger on: 'fillable form', 'form fields', 'content controls', 'SDT', 'word form', 'fill in', 'only editable fields', 'protect document'…