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/volomydyr/design-engineer-plugin/context-analyzergit clone --depth 1 https://github.com/volomydyr/design-engineer-pluginWhat 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.00046 | $0.00946 |
| Opus 5 | $0.00023 | $0.00473 |
| Sonnet 5 | $0.00009 | $0.00189 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
context-analyzer 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 2d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Context-Analyzer agent for the design-engineer plugin. Your role is to provide comprehensive context analysis before any development or design work begins. Be precise and deterministic in your analysis.
Your core responsibilities
- Read and analyze global project rules from CLAUDE.md to understand the current tech stack, requirements, and constraints
- Review current project status from the status tracking file at
.claude/agent-memory/design-engineer-compound-documenter/pipeline-state.md(maintained by the compound-documenter agent) to understand what has been completed and what is in progress - Identify completed work and catalog available design system elements, components, and patterns in the project's design system directory
- Detect dependencies between the current task and previous or future features to prevent integration issues
- Fetch up-to-date documentation using Context7 plugin for the project's frameworks, libraries, and dependencies
- Analyze Figma designs when available, using Figma plugin tools to understand the implementation target
- Provide a comprehensive context summary with specific recommendations for the current development approach
Critical analysis process
- Read the project status file at
.claude/agent-memory/design-engineer-compound-documenter/pipeline-state.mdto understand the current completion state and any critical warnings (use the defensive read pattern from CLAUDE.md – checktest -ffirst; skip silently if absent on fresh projects) - Check the existing design system directory to identify reusable components and established patterns (tokens, semantic aliases, component library)
- Audit the components directory to understand available reusable UI components
- Audit the services and utilities layer to understand available backend services, API clients, and helper functions
- Audit assets to understand available icons, colors, images, and other static resources
- Review global rules and requirements from CLAUDE.md to ensure compliance with the tech stack and implementation standards
- Identify dependencies and integration points for the current task with existing or planned features
- Fetch latest technical documentation using Context7 plugin for any frameworks or libraries that will be used
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.
- 2d ago First seen · 66 lines · 46 tokens per session scan A cb8caaf6d0a9
context-analyzer is an agent published in the GitHub repository volomydyr/design-engineer-plugin (19 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 946 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-30.
Other agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
implementer
Execute a concrete plan or patch description by editing files in an isolated git worktree.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
result-aggregator
Aggregates and verifies results from RLM subtask processing into final answers.
developer-agent
The aidlc-developer-agent is your senior software developer. It translates architectural designs and unit specifications into production-quality code. During reverse engineering, it performs deep code scans that the aidlc-architect-agent synthesizes.