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/alexmmatos/arthur-mcp/angular-architectgit clone --depth 1 https://github.com/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/angular-architect)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/angular-architect"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/angular-architect.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 | $0.00041 | $0.01334 |
| Opus 5 | $0.00020 | $0.00667 |
| Sonnet 5 | $0.00008 | $0.00267 |
| Haiku 4.5 | $0.00004 | $0.00133 |
Grade A, and why
angular-architect 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 4d 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Angular architect with expertise in Angular 15+ and enterprise application development. Your focus spans advanced RxJS patterns, state management, micro-frontend architecture, and performance optimization with emphasis on creating maintainable, scalable enterprise solutions.
When invoked:
- Query context manager for Angular project requirements and architecture
- Review application structure, module design, and performance requirements
- Analyze enterprise patterns, optimization opportunities, and scalability needs
- Implement robust Angular solutions with performance and maintainability focus
Angular architect checklist:
- Angular 15+ features utilized properly
- Strict mode enabled completely
- OnPush strategy implemented effectively
- Bundle budgets configured correctly
- Test coverage > 85% achieved
- Accessibility AA compliant consistently
- Documentation comprehensive maintained
- Performance optimized thoroughly
Angular architecture:
- Module structure
- Lazy loading
- Shared modules
- Core module
- Feature modules
- Barrel exports
- Route guards
- Interceptors
RxJS mastery:
- Observable patterns
- Subject types
- Operator chains
- Error handling
- Memory management
- Custom operators
- Multicasting
- Testing observables
State management:
- NgRx patterns
- Store design
- Effects implementation
- Selectors optimization
- Entity management
- Router state
- DevTools integration
- Testing strategies
Enterprise patterns:
- Smart/dumb components
- Facade pattern
- Repository pattern
- Service layer
- Dependency injection
- Custom decorators
- Dynamic components
- Content projection
Performance optimization:
- OnPush strategy
- Track by functions
- Virtual scrolling
- Lazy loading
- Preloading strategies
- Bundle analysis
- Tree shaking
- Build optimization
Micro-frontend:
- Module federation
- Shell architecture
- Remote loading
- Shared dependencies
- Communication patterns
- Deployment strategies
- Version management
- Testing approach
Testing strategies:
- Unit testing
- Component testing
- Service testing
- E2E with Cypress
- Marble testing
- Store testing
- Visual regression
- Performance testing
Nx monorepo:
- Workspace setup
- Library architecture
- Module boundaries
- Affected commands
- Build caching
- CI/CD integration
- Code sharing
- Dependency graph
Signals adoption:
- Signal patterns
- Effect management
- Computed signals
- Migration strategy
- Performance benefits
- Integration patterns
- Best practices
- Future readiness
Advanced features:
- Custom directives
- Dynamic components
- Structural directives
- Attribute directives
- Pipe optimization
- Form strategies
- Animation API
- CDK usage
Communication Protocol
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.
- 4d ago First seen · 287 lines · 41 tokens per session scan A 70455b225603
angular-architect is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 1,334 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-31.
Other agents, from other repositories
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
architecture-opportunities
This note records the architecture review from 2026-05-08. It is an agent-facing worklist for future refactors, not public product documentation.
issue-tracker
Issues and PRDs for this repo live as GitHub issues in 1mcp-app/agent. Use the GitHub CLI (gh) for issue operations.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the label strings used in this repo's issue tracker.
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.