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/IgniteUI/igniteui-angularWrote 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/igniteui/igniteui-angular/theming-styles-agent)<a href="https://agentmods.dev/agents/igniteui/igniteui-angular/theming-styles-agent"><img src="https://agentmods.dev/badge/agents/igniteui/igniteui-angular/theming-styles-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/igniteui/igniteui-angular/theming-styles-agent"><img src="https://agentmods.dev/badge/agents/igniteui/igniteui-angular/theming-styles-agent.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.01299 |
| Opus 5.5 | $0.00013 | $0.00520 |
| Sonnet 5.5 | $0.00007 | $0.00260 |
| Haiku 4.5 | $0.00003 | $0.00130 |
Grade A, and why
theming-styles-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 1mo 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 1mo ago Changed · +1 lines 00c04121f12c
- 1mo ago First seen · 152 lines · 33 tokens per session scan A 88cc3a518547
theming-styles-agent is an agent published in the GitHub repository IgniteUI/igniteui-angular (599 stars, last pushed yesterday), with no licence file. It adds 33 tokens to every session and 1,299 once invoked, about $0.0001 per session on Opus 5.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
a11y-full-page-audit
Use for full page or route-level WCAG accessibility audits. Triggers when the user asks to 'audit the page', 'full a11y audit', 'accessibility sign-off', or 'WCAG page audit'. For single component audits use a11y-component-audit.
sdk-setup
Use when the user wants to create a new TypeScript SDK from an OpenAPI spec, set up an SDK in their project, or needs guidance choosing between standalone vs monorepo approaches. Also triggers when the user says "I want to call an API", "generate a client from a spec", "set up SDK", or "create API client" without…
logic-design
Decide where new application logic belongs — component shape, logic layer, store variant — and return a recommendation with the schematic to run and what to verify. Use the logic-review agent for existing code.
logic-review
Review existing components, services, and stores for misplaced logic and report findings with file, line, the rule broken, and the fix. Use the logic-design agent to decide where something new should go.
a11y-write-playwright-tests
Write Playwright accessibility tests for a component or page: axe scan file and keyboard-only variant. Triggers when the user asks to 'add a11y tests', 'write axe test', 'add keyboard test', or 'create accessibility test for X'.
otter-migration
Use when upgrading @o3r, @ama-mfe, or @ama-sdk packages, running an Otter/Angular migration, or bumping Otter versions across a monorepo. Plans the migration, bumps versions, resolves peer-dependency conflicts, reads migration schematics and applies the equivalent code changes manually, regenerates any SDK produced…