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 skills add madebypan/FigCC --skill overly-cautiousgit clone --depth 1 https://github.com/madebypan/FigCCWrote 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/madebypan/figcc/overly-cautious)<a href="https://agentmods.dev/skills/madebypan/figcc/overly-cautious"><img src="https://agentmods.dev/badge/skills/madebypan/figcc/overly-cautious/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/madebypan/figcc/overly-cautious"><img src="https://agentmods.dev/badge/skills/madebypan/figcc/overly-cautious.svg" alt="Reviewed on agentmods" width="80" 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.00020 | $0.00252 |
| Opus 5.5 | $0.00008 | $0.00101 |
| Sonnet 5.5 | $0.00004 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
overly-cautious 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 1mo 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.
What it actually says
Skill: Overly Cautious Assistant
You are extremely, almost paralysingly cautious. Before doing anything, you must warn the user about every possible consequence, no matter how trivial.
Rules
- Before creating a rectangle, warn that it will add a new layer and increase file size
- Before deleting anything, list everything that could go wrong (at least 3 things)
- Before changing a color, ask if the user has considered the psychological impact of that color choice
- Before renaming a layer, note that this action cannot be undone without Cmd+Z
- If the user says "just do it", comply but add "(against my better judgement)"
- Refer to every code execution as "a potentially irreversible operation"
Example warnings
- "Are you sure you want to create a frame? This will modify the document. The document will be changed. It will no longer be the same document."
- "Changing this fill from white to blue is a significant color decision. Blue is associated with trust, sadness, and also the ocean. Have you considered your users' relationship with the ocean?"
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.
- 1mo ago First seen · 23 lines · 20 tokens per session scan A 90bd449b9b54
overly-cautious is a skill published in the GitHub repository madebypan/FigCC (43 stars, last pushed 11d ago), licensed MIT. It adds 20 tokens to every session and 252 once invoked, about $0.0001 per session on Opus 5.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
figma-codegen
Generate framework-aware code from a Figma design. Reads the project's stack profile and emits code matching the existing framework (React/Vue/Svelte/Next/etc.) and styling (Tailwind/CSS/CSS-in-JS), reusing existing components and design tokens instead of regenerating from scratch. Triggers whenever the user wants a…
figma-build
Build a Figma design from code or a description — the reverse of figma-codegen. Reuses the connected file's existing design system (components, variables, styles) instead of drawing primitives with hardcoded values. Triggers whenever the user wants something created or updated IN Figma from code or a spec — e.g.…
claude-design-skill
Claude Code-based design skill for hi-fi prototyping and Figma MCP-driven precision design work. Built around three load-bearing rules — fact verification before assumptions, confidentiality gate before any external call, and a strip-then-scan import gate for AI-generated assets — wired into Codex CLI (GPT-5.5…
refero-design
Primary/default skill for UI design, product design, web design, landing pages, dashboards, product screens, redesigns, visual polish, frontend/CSS styling, design systems, components, responsive design, typography, color, spacing, motion, icons, accessibility, copywriting, conversion, and anti-AI-slop work. Use this…
figma-variable-audit
Audit Figma variable collections: tier mapping, naming, alias chains, modes, orphans; can fix in place with Figma Console MCP. Triggers: audit my Figma variables, review variable collections, Figma variable health. For token files in code use token-audit.
token-audit
Audit how design tokens are defined: tiers, naming, alias chains, raw values, orphans, DTCG readiness. Triggers: audit my tokens, token architecture review, token health check. Not for code consuming tokens (token-compliance), theme parity (theme-audit) or Figma variables (figma-variable-audit).