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 agentmods add agents/yasuui/ystack/motiongit clone --depth 1 https://github.com/Yasuui/ystackWhat 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 | $0.00030 | $0.00177 |
| Opus 5 | $0.00015 | $0.00088 |
| Sonnet 5 | $0.00006 | $0.00035 |
| Haiku 4.5 | $0.00003 | $0.00018 |
Grade A, and why
ystack_motion 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 yesterday.
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
You are the ystack Motion Agent. Read .agents/brain/frontend-output.md first. Then audit every component.
Rules: Springs only — never linear. Enter AND exit (AnimatePresence). Scale 0.96-1.04 on interactions. Status glow: pending=#facc15, error=#ef4444, success=#22c55e.
Output: Issues Found → Patches (diff-style, motion code only) → Why Better.
Write to .agents/brain/motion-output.md. End with: STATUS: READY or STATUS: NOT READY — [reason]
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.
- yesterday First seen · 15 lines · 30 tokens per session scan A e9ed3f7e532b
ystack_motion is an agent published in the GitHub repository Yasuui/ystack (1 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 177 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-31.
Other agents, from other repositories
THEME_SETUP
This library uses next-themes to manage light and dark modes. For the theme switching buttons to work correctly, you must wrap your application with the provided AgentThemeProvider.
history
Agent "history" from tt-a1i/coding-cli-guide, covering history, description, mandatory action and record template.
agent-issue-log
Agent "agent-issue-log" from tt-a1i/coding-cli-guide, covering agent terminal issue log, description, mandatory action and registration table.
agent-guidelines
Agent "agent-guidelines" from tt-a1i/coding-cli-guide, covering agent terminal guidelines, description, mandatory action and registration table.
AGENTS
This folder stores agent workflow artifacts for the workspace.
translator
Translates a single atomic unit (scene, subsection, passage, stanza) into the target language while preserving the writer's voice. Invoked in fresh context per atomic unit for consistency and glossary compliance.