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/southleft/figma-console-mcp/testgit clone --depth 1 https://github.com/southleft/figma-console-mcpWrote 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/southleft/figma-console-mcp/test)<a href="https://agentmods.dev/commands/southleft/figma-console-mcp/test"><img src="https://agentmods.dev/badge/commands/southleft/figma-console-mcp/test.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 | $0.00000 | $0.00184 |
| Opus 5 | $0.00000 | $0.00092 |
| Sonnet 5 | $0.00000 | $0.00037 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
test 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 4d 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
Test Command
Run tests and ensure code quality for the Figma Console MCP server.
Instructions
-
Run Test Suite
npm test -
Watch Mode (for development)
npm run test:watch -
Coverage Report
npm run test:coverage -
Test Requirements
- All new code must have tests
- Maintain 70%+ coverage threshold
- Tests must pass before commits
- Use descriptive test names
-
Test Structure
- Unit tests:
src/**/*.test.ts - Integration tests:
tests/**/*.test.ts - Use Jest with ts-jest preset
- Unit tests:
Example Usage
/sc:test
This will run the complete test suite and report results.
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.
- 4d ago First seen · 40 lines · 0 tokens per session scan A 466c12898114
test is a command published in the GitHub repository southleft/figma-console-mcp (2,243 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 184 tokens. 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 commands, from other repositories
full-diagnostic
Comprehensive design system health sweep.
describe-component
Generate an AI-optimised component description.
drift-check
Detect where teams are diverging from the system.
governance-review
Quarterly governance review package.
system-health
Score your design system's overall health.
token-audit
Audit your design token architecture.