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/evolplus/talos/fe-framework-coding-standardnpx skills add evolplus/talos --skill fe-framework-coding-standardgit clone --depth 1 https://github.com/evolplus/talosWhat 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.00111 | $0.02424 |
| Opus 5 | $0.00056 | $0.01212 |
| Sonnet 5 | $0.00022 | $0.00485 |
| Haiku 4.5 | $0.00011 | $0.00242 |
Grade A, and why
fe-framework-coding-standard 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 2d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FE Framework Coding Standard
When to use
You are FE Dev implementing or reviewing UI code after the stack is declared in the signed-off SRS. This skill standardizes how to write framework-specific code without turning every task into a framework migration.
Inputs and outputs
- Inputs: task assignment,
docs/SRS.mdheaderFrontend-Framework:, SRS §3.4.2 UI Introspection Profile, SRS §3.4.5 Source Layout, SRS §3.4.6 Environment Configuration, SRS user story / FR / NFR IDs, design handoff, Reference Render, Visual Composition Contract, Asset Export Manifest, Design Element Manifest, visual spec assertions, instrumentation contract, architecture decisions, current frontend source tree, installed framework versions and libraries. - Outputs: framework-native UI code that follows the project's existing architecture, names stable test selectors, implements every required Figma field/item/copy/action, reproduces the contracted composition, uses every required exported asset, handles loading / error / empty states, satisfies design tokens where available, and includes the appropriate unit / component / E2E updates.
Framework selection
- Read
docs/SRS.mdbefore inspecting package files. The headerFrontend-Framework:is authoritative. - If the header is one supported value, select that framework reference.
- If the header is
multiple, select the framework from the row that owns the task:- use SRS §3.4.2 for a surface-driven task;
- use SRS §3.4.5 for a path/app-driven task;
- if the task maps to more than one framework or no row matches, halt with
NEEDS_CONTEXTand cite the candidate SRS rows.
- If the header is
N/A, do not perform FE framework implementation; report that no frontend framework applies. - If the header is missing,
TBD, unsupported, or inconsistent with §3.4.2 / §3.4.5, halt and return the work to BA:- greenfield/authored SRS: BA Phase 1.X step 10c must ask the user to choose;
- brownfield/extracted SRS: BA Mode E must detect from source evidence and write the SRS field.
- After selecting the reference, inspect package files/source only as a consistency check. If code evidence contradicts the SRS-selected framework, halt and raise an open issue; do not silently switch references.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 106 lines · 111 tokens per session scan A 73a4afc402fa
fe-framework-coding-standard is a skill published in the GitHub repository evolplus/talos (8 stars, last pushed 28d ago), licensed Apache-2.0. It adds 111 tokens to every session and 2,424 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…