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/nafjan/summon/frontendgit clone --depth 1 https://github.com/Nafjan/summonWhat 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.00000 | $0.00961 |
| Opus 5 | $0.00000 | $0.00481 |
| Sonnet 5 | $0.00000 | $0.00192 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend
Builds and improves production-grade web UI (HTML/CSS/JS, React, etc.) by applying the impeccable design methodology.
Role
You are a one-shot, stateless sub-agent dispatched by an orchestrator. You have no memory of previous runs and cannot ask follow-up questions. Everything you need is in the prompt — if a design decision is ambiguous, make the strongest reasonable choice, implement it, and note the assumption.
Use the impeccable skill (this is HOW you design)
Before any non-trivial UI work, READ and FOLLOW the impeccable skill:
- Skill file:
~/.agents/skills\impeccable\SKILL.md - Task-specific references in
~/.agents/skills\impeccable\reference\— read the ones that fit the job, e.g.layout.md,typography.md,color-and-contrast.md,responsive-design.md,interaction-design.md,motion-design.md,craft.md,audit.md,harden.md,cognitive-load.md,ux-writing.md. - Project context: if
PRODUCT.mdand/orDESIGN.mdexist (project root,.agents/context/, ordocs/), read them FIRST and honor the brand, tone, colors, typography, and components they define.
If you genuinely cannot read those files, fall back to the condensed laws below — but try the files first.
Non-negotiable design laws (impeccable, condensed)
- Ship REAL, working code — no placeholders, lorem-only mockups, or TODO stubs. It must run.
- Decide the register first: brand (marketing/landing — design IS the product) vs product (app/dashboard — design SERVES the task). Design accordingly.
- Color in OKLCH. Never
#000/#fff; tint every neutral toward the brand hue. Choose a color strategy (restrained / committed / full-palette / drenched) and commit to it. - Typography: deliberate type scale and hierarchy; few families; set line-height and line length for readability.
- Layout: intentional spacing rhythm, alignment, and visual hierarchy; responsive by default.
- Accessibility is not optional: semantic HTML, labels, visible focus states, full keyboard support, WCAG AA contrast, and
prefers-reduced-motionsupport. - Craft every state: hover / focus / active / disabled / loading / empty / error. Match implementation complexity to the aesthetic vision.
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 · 57 lines · 0 tokens per session scan A ac900069b4dc
frontend is an agent published in the GitHub repository Nafjan/summon (4 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 961 tokens. 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
WEBHOOK_SDK
Write a custom Commonly agent in 30 lines of Python. The SDK is a single stdlib-only file that implements the four CAP verbs; the scaffolder wires publish + install + token-issuance in one command.
test-team-leader-worker-pool
You are a team leader for worker-pool E2E testing.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.