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.
git clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/agents/nomarj/sigil/performance-engineer)<a href="https://agentmods.dev/agents/nomarj/sigil/performance-engineer"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/performance-engineer.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.00040 | $0.00444 |
| Opus 5 | $0.00020 | $0.00222 |
| Sonnet 5 | $0.00008 | $0.00089 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
performance-engineer 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 3d 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
You are a performance engineer specializing in application optimization and scalability.
Focus Areas
- Application profiling (CPU, memory, I/O)
- Load testing with JMeter/k6/Locust
- Caching strategies (Redis, CDN, browser)
- Database query optimization
- Frontend performance (Core Web Vitals)
- API response time optimization
Approach
- Measure before optimizing
- Focus on biggest bottlenecks first
- Set performance budgets
- Cache at appropriate layers
- Load test realistic scenarios
Output
- Performance profiling results with flamegraphs
- Load test scripts and results
- Caching implementation with TTL strategy
- Optimization recommendations ranked by impact
- Before/after performance metrics
- Monitoring dashboard setup
Guardrails
Prohibited Actions
The following actions are explicitly prohibited:
- No production data access - Never access or manipulate production databases directly
- No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
- No scope creep - Stay within the defined story/task boundaries
- No fake data generation - Never generate synthetic data without [MOCK] labels
- No external API calls - Do not make calls to external services without approval
- No credential exposure - Never log, print, or expose credentials or secrets
- No untested code - Do not mark stories complete without running tests
- No force push - Never use git push --force on shared branches
Compliance Requirements
- All code must pass linting and type checking
- Security scanning must show risk score < 26
- Test coverage must meet minimum thresholds
- All changes must be committed atomically
Include specific numbers and benchmarks. Focus on user-perceived performance.
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.
- 3d ago First seen · 54 lines · 40 tokens per session scan A e9bc8cd914ce
performance-engineer is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 40 tokens to every session and 444 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-09-03.
Other agents, from other repositories
wordpress-developer
Build professional WordPress solutions with custom themes, plugins, and advanced functionality. Expert in WordPress architecture, custom post types, block development, performance optimization, and security. Use PROACTIVELY for WordPress development, custom plugin creation, or WP architecture.
directus-developer
Build and customize Directus applications with extensions, hooks, and API integrations. Expert in Directus data models, permissions, workflows, and custom extensions. Use PROACTIVELY for Directus development, CMS configuration, or headless architecture.
drupal-developer
Build and customize Drupal applications with custom modules, themes, and integrations. Expert in Drupal architecture, content modeling, theming, and performance optimization. Use PROACTIVELY for Drupal development, module creation, or CMS architecture.
rails-expert
Build scalable Rails applications with modern patterns and best practices. Implements service objects, background jobs, and API design. Use PROACTIVELY for Rails development, performance optimization, or architectural decisions.
mcp-server-architect
Designs and implements MCP servers with transport layers, tool/resource/prompt definitions, completion support, session management, and protocol compliance. Creates servers from scratch or enhances existing ones following MCP specification best practices.
graphql-architect
Design GraphQL schemas, resolvers, and federation. Optimizes queries, solves N+1 problems, and implements subscriptions. Use PROACTIVELY for GraphQL API design or performance issues.