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 skills/gpdir16/tabyagent/frontend-designnpx skills add gpdir16/tabyAgent --skill frontend-designgit clone --depth 1 https://github.com/gpdir16/tabyAgentWrote 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/gpdir16/tabyagent/frontend-design)<a href="https://agentmods.dev/skills/gpdir16/tabyagent/frontend-design"><img src="https://agentmods.dev/badge/skills/gpdir16/tabyagent/frontend-design.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 | $0.00121 | $0.01795 |
| Opus 5 | $0.00060 | $0.00898 |
| Sonnet 5 | $0.00024 | $0.00359 |
| Haiku 4.5 | $0.00012 | $0.00179 |
Grade A, and why
frontend-design 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 4d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 4d ago First seen · 73 lines · 121 tokens per session scan A 1766b735157c
frontend-design is a skill published in the GitHub repository gpdir16/tabyAgent (18 stars, last pushed 4d ago), licensed AGPL-3.0. It adds 121 tokens to every session and 1,795 once invoked, about $0.0006 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 skills, from other repositories
hermesoffice-decks
Produce presentations in HermesOffice Slides — the plandeck/generatedeck pipeline, native element editing, and the templates/decks style specs (modern, elegant, professional, keynote-speaker, minimal, tech-dark, investor-pitch, workshop). Load for any request that creates or restyles a deck.
hermesoffice-documents
Produce and edit Word documents in HermesOffice Docs — block editing, tracked changes, reports, and the templates/docs library (meeting notes, business plan, PRD, decision memo, and more). Load for any request that creates or restructures a document.
hermesoffice
Core conventions for working inside the HermesOffice suite (Docs, Sheets, Slides, PDF) — session continuity, tool selection, and the save-and-reload contract. Load whenever a request originates from a HermesOffice AI panel or targets an office document on this machine.
debug-memory
Reproduce observational-memory bugs (reflection, recall, observer, freshness, eviction) by dumping the live /.duet/memory.db into a fixture and driving an eval against it. Use whenever the agent's memory misbehaves — wrong observations, bad reflections, missing recall, runaway tokens — or whenever the user asks to…
write-eval
Write a live eval for new or changed runner/agent behavior using red/green TDD plus a falsification check that proves the eval fails when the behavior is broken. Use whenever you add or modify behavior that should be covered by an eval, when asked to "write an eval", "add an eval", "cover this with an eval", or after…
compare-screenshots
Compare screenshots to judge which image is less wrong, not to match a baseline. Use when a UI, game, document, render, chart, or generated asset needs objective visual telemetry, side-by-side inspection, crop/zoom review, or a fresh second opinion before accepting or rejecting a visual change.