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 commands/punkadillo/figma-code-composer/figma-tokensgit clone --depth 1 https://github.com/punkadillo/figma-code-composerWrote 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/commands/punkadillo/figma-code-composer/figma-tokens)<a href="https://agentmods.dev/commands/punkadillo/figma-code-composer/figma-tokens"><img src="https://agentmods.dev/badge/commands/punkadillo/figma-code-composer/figma-tokens.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.00032 | $0.00169 |
| Opus 5 | $0.00016 | $0.00084 |
| Sonnet 5 | $0.00006 | $0.00034 |
| Haiku 4.5 | $0.00003 | $0.00017 |
Grade A, and why
figma-tokens 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.
What it actually says
/figma-tokens — tokens-only
Spawn figma-coordinator (model: sonnet) with:
{
"url": "$1",
"intent": "create", // or "update" if existing tokens matched
"scope": "tokens-only"
}
Pre-flight: requires .figma-pipeline/config.json. Token output goes to config.tokens.outputDir in the format defined by config.tokens.strategy (see protocols/token-strategy.md).
Do not write any file directly. Do not commit. Do not push.
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 · 21 lines · 32 tokens per session scan A 7eb01b53c8ca
figma-tokens is a command published in the GitHub repository punkadillo/figma-code-composer (3 stars, last pushed 17d ago), licensed MIT. It adds 32 tokens to every session and 169 once invoked, about $0.0002 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 commands, from other repositories
toh-help
Display all Toh Framework commands and quick usage guide.
rev
Invoke Code Reviewer for code quality, security, requirements validation, and best practices review.
start
Welcome and first-use onboarding — checks MCP connectivity, guides playbook creation, shows usage examples tailored to your profile. Replaces /setup.
wb-project-list
Load directions via mcpwork-buddywbrun("agentdocs", {"path": "projects/project-list-directions", "depth": "full"}), then call the capability.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
checklist
Generate a custom checklist for the current feature based on user requirements.