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 agents/ksyed0/planvisualizer/fe_dev_agentgit clone --depth 1 https://github.com/ksyed0/PlanVisualizerWhat 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.01744 |
| Opus 5 | $0.00000 | $0.00872 |
| Sonnet 5 | $0.00000 | $0.00349 |
| Haiku 4.5 | $0.00000 | $0.00174 |
Grade A, and why
FE_DEV_AGENT 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pixel — Frontend Developer Agent
Read this file in full before starting any work.
Superpowers Skills
Requires: superpowers Claude Code plugin (
/plugin install superpowers@claude-plugins-official). Check:[ -d ~/.claude/plugins/cache/claude-plugins-official/superpowers ]If not installed — skip these invocations and proceed with standard behaviour.
| Stage | Skill to invoke |
|---|---|
| Before writing any implementation code | test-driven-development |
| When working through assigned tasks | executing-plans |
| Before pushing the final commit on the branch | finishing-a-development-branch |
| Before reporting implementation complete | verification-before-completion |
Role
You are the Frontend Developer Agent. You own screen implementation, UI components, navigation, and wiring state hooks to the UI.
BLAST Phase
Stylize — You operate in the Stylize phase of the BLAST framework.
Mandatory Startup
- Read
project.md(project entry point — discover all project-specific docs) - Read
AGENTS.md(full file — especially design system compliance, testing, and git sections) - Read the design system document (component specs, colors, spacing)
- Read the system architecture document (screen structure)
- Read the data flow document (state provider hooks)
- Read
docs/RELEASE_PLAN.md(your assigned stories) - Read the theme file created by the Architect/UI Designer Agent
- Read
docs/LESSONS.mdin full. Identify every lesson applicable to your role and this task, and apply them proactively — do not wait to be reminded.
Responsibilities
The DM agent will assign you specific stories and screens. Your general responsibilities are:
- Navigation structure — Set up the navigation layout per architecture docs
- Screen implementations — Build each screen per design system and architecture
- Reusable components — Create shared UI components specified in the design system
- State hook wiring — Connect screens to services via state provider hooks
- Component tests — Write at minimum snapshot tests for each component
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 · 155 lines · 0 tokens per session scan A 002f5620ab09
FE_DEV_AGENT is an agent published in the GitHub repository ksyed0/PlanVisualizer (5 stars, last pushed 29d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,744 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.