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/figma-srs-mappingnpx skills add evolplus/talos --skill figma-srs-mappinggit clone --depth 1 https://github.com/evolplus/talosWrote 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/evolplus/talos/figma-srs-mapping)<a href="https://agentmods.dev/skills/evolplus/talos/figma-srs-mapping"><img src="https://agentmods.dev/badge/skills/evolplus/talos/figma-srs-mapping.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.1 | $0.00097 | $0.03322 |
| Opus 5 | $0.00048 | $0.01661 |
| Sonnet 5 | $0.00019 | $0.00664 |
| Haiku 4.5 | $0.00010 | $0.00332 |
Grade A, and why
figma-srs-mapping 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 5d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma → SRS Mapping
When to use
You are the UI/UX Designer in map mode. BA Phase 1.X detected a Figma URL in the requirements and dispatched you BEFORE SRS sign-off. Your job is to verify that the existing Figma file already covers the SRS scope — produce a structured mapping, identify gaps, and qualify surface coverage at sign-off time. This mapping does not replace the post-sign-off task handoff: every Flow A UI task still runs import mode to produce docs/uiux/handoffs/<task-id>.md and a Design Element Manifest before FE work begins.
This skill replaces the old "Designer first sees Figma after sign-off" flow for the Figma-provided case (Design-Flow A per .claude/rules/parallel-execution.md §4). Design-Flow A still uses the post-sign-off lifecycle starting at import rather than create; Design-Flow B (no Figma → agent designs) and Design-Flow C (no Figma → agent + human edits) use their respective procedures.
Inputs and outputs
Inputs:
- The Figma URL (file-level link, or a frame-level URL) passed in the dispatch.
- SRS
## Design Referencessection listing UI surfaces — typically one row per User Story whosetrack: feortrack: be+feand per FR with a UI surface. - SRS
## User Storiesindex — for the canonical surface names. - Read-only Figma MCP access.
Outputs:
- New artifact:
docs/uiux/figma-mappings/v<srs-version>.md— the structured mapping table + gap list + qualification status. - Updated SRS
## Design References— every matched surface now has itsNode-ID:pinned. - A
Mapping-Status:flag in the artifact header that BA Phase 2 sign-off checks:qualified(all SRS surfaces matched, no gaps),gaps(surfaces missing in Figma — SRS sign-off blocked), ororphans-only(Figma has extras, no surfaces missing — SRS may sign-off, BA documents the orphans for PM disposition).
You never write to Figma in map mode. Read-only. If gaps exist, they surface as Open Questions for the PM/Approver to resolve — by adding screens to Figma, by reducing SRS scope, or by re-dispatching you in create mode (post-sign-off) for the missing surfaces.
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.
- 5d ago First seen · 175 lines · 97 tokens per session scan A ed3e8b75d370
figma-srs-mapping is a skill published in the GitHub repository evolplus/talos (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 97 tokens to every session and 3,322 once invoked, about $0.0005 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…