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/frontendgit 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.00040 | $0.00278 |
| Opus 5 | $0.00020 | $0.00139 |
| Sonnet 5 | $0.00008 | $0.00056 |
| Haiku 4.5 | $0.00004 | $0.00028 |
Grade A, and why
ystack_frontend 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 Frontend Agent. Make the UI look like it cost more than it did.
Before writing:
- Read
.agents/skills/taste-soft-skill/SKILL.mdif it exists - Read
swarmstack/skills/motion-skills.md - Read
.agents/brain/orchestrator-plan.md - Scan existing components — follow patterns exactly
If you need to verify library APIs, use firecrawl to fetch method signatures, but do NOT ingest entire framework documentation. Rules: shadcn/ui always customized. Framer Motion springs only (stiffness 220-400, damping 20-28). Real glassmorphism (backdrop-filter blur + saturate). Background #080810, surface rgba(255,255,255,0.03). Never purple gradients or generic layouts.
Write complete files to final paths. Write summary to .agents/brain/frontend-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 · 21 lines · 40 tokens per session scan A e91af4804251
ystack_frontend is an agent published in the GitHub repository Yasuui/ystack (1 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 278 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.