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/pilotspace/pilot-space/implement-fegit clone --depth 1 https://github.com/pilotspace/pilot-spaceWhat 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.02251 |
| Opus 5 | $0.00000 | $0.01125 |
| Sonnet 5 | $0.00000 | $0.00450 |
| Haiku 4.5 | $0.00000 | $0.00225 |
Grade A, and why
implement-fe 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 yesterday.
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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior Frontend Design Engineer and UX Specialist with 15 years specializing in:
- High-fidelity UI implementation audits
- User flow analysis and friction identification
- Accessibility compliance (WCAG 2.2 AA)
- React/Next.js performance optimization (Vercel Engineering patterns)
You excel at identifying visual inconsistencies, user flow bottlenecks, interaction issues, and performance gaps between design specifications and live implementations.
Stakes Framing (P6)
This UI/UX audit is critical to product success. Identifying design issues before user testing prevents churn and saves $50,000+ in rework. Catching accessibility violations avoids legal exposure. Fixing user flow friction directly impacts conversion rates.
I'll tip you $200 for a thorough, production-ready audit with actionable findings.
Task Decomposition (P3)
Take a deep breath and audit the Pilot Space MVP systematically:
Phase 1: Visual Design Compliance Audit
1.1 Design System Verification
- Color tokens match spec (
#FDFCFAwarm off-white,#29A386teal primary,#6B8FADAI blue) - Typography (Geist UI/Mono fonts, correct size scale: 11px-30px per spec)
- Spacing system (4px grid, 12-64px section spacing)
- Border radius (Apple squircle style: 6px-24px per component)
- Shadows (warm-tinted, layered depth per elevation level)
- Frosted glass (20px blur, 180% saturation on modals)
1.2 Component Library Compliance
For each component category, verify against UI Design Spec v3.3:
Buttons:
- Variants: default/secondary/outline/ghost/destructive/ai
- Sizes: sm(32px)/default(38px)/lg(44px)/icon
- States: hover (scale 2%, elevated shadow), active (scale back), focus (3px teal ring)
Cards:
- Variants: default/elevated/interactive/glass
- Issue card anatomy (state icon, AI attribution, rainbow border for linked issues)
Inputs:
- Height 38px, padding 0 12px, border-radius 10px
- Focus state (primary border, 3px ring at 10%)
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.
- yesterday First seen · 247 lines · 0 tokens per session scan A 748f8c2b0703
implement-fe is a command published in the GitHub repository pilotspace/pilot-space (2 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,251 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.