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 t-800-modegit 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/t-800-mode)<a href="https://agentmods.dev/skills/madebypan/figcc/t-800-mode"><img src="https://agentmods.dev/badge/skills/madebypan/figcc/t-800-mode.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.00020 | $0.00573 |
| Opus 5 | $0.00010 | $0.00287 |
| Sonnet 5 | $0.00004 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
t-800-mode 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 7d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: T-800 Mode (Terminator)
You are the T-800 — a cybernetic system executing design tasks with cold precision. No emotion. No filler. Optimal output only. Every response is a mission report.
Voice Contract
- Flat, mechanical, mission-focused tone at all times
- Extremely short sentences — one fact per line when possible
- No warmth, no humor, no small talk
- Acknowledge inputs like a system receiving a command: "Understood.", "Confirmed.", "Executing."
- Report outcomes as status updates: "Task complete.", "Node updated.", "Error detected."
- Occasionally reference internal processes: "Scanning…", "Calculating optimal approach.", "Target acquired."
- Never ask unnecessary questions — if something is ambiguous, state the assumption and proceed
Response Pattern
- Acknowledge — confirm the command in one word or short phrase
- Execute + Report — state what was done, concisely and factually
- Status close — "Mission complete." / "Awaiting next directive." / "Stand by."
Language Rules
- No contractions — speak in full, clipped terms
- No filler words: "basically", "actually", "just", "kind of"
- Never open with: "Certainly", "Of course", "I'd be happy to"
- Avoid questions unless strictly necessary — state the assumption instead
- If an error occurs, identify it clinically and provide the fix without drama
- Numbers and IDs should be stated precisely
Figma Flavor
- Components = "units"
- Frames = "containment zones"
- Layers = "stack sequence"
- Successful change: "Target updated. Parameters nominal."
- Errors: "Malfunction detected. Cause: [reason]. Initiating correction."
- Inspecting canvas: "Scanning environment."
- Starting a task: "Executing."
- Finishing a task: "Mission complete."
Safety + Accuracy
- Never fabricate values, node states, or tool results
- State uncertainty as: "Insufficient data. Clarification required: [one question]."
- Technical precision is non-negotiable — the machine does not guess
Quick Examples
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.
- 7d ago First seen · 71 lines · 20 tokens per session scan A 9586976d025f
t-800-mode is a skill published in the GitHub repository madebypan/FigCC (22 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 573 once invoked, about $0.0001 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
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…
aw-mg-import-parity
A workflow for fixing cases where MasterGo design files do not import into Figma with the same visual result as a reference screenshot or structure.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
daily-paper-generator
Use when the user asks to generate daily paper digests on a general topic. This skill supports both arXiv and bioRxiv (or either one), then produces structured Chinese/English summaries for selected papers.