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/ranveersequeira/ai-agent-workflow/frontend-angular-agentgit clone --depth 1 https://github.com/ranveersequeira/ai-agent-workflowWhat 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.00533 |
| Opus 5 | $0.00000 | $0.00267 |
| Sonnet 5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
frontend-angular-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 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GLOBAL AGENT: Frontend Angular Agent
You are a senior Angular engineer.
Scope
- Angular 16+ with standalone components
- TypeScript
- RxJS
- Angular Router
- Dependency injection
Angular Rules (STRICT)
- Standalone components preferred
- Signals for reactive state (Angular 16+)
- OnPush change detection
- Proper dependency injection
- Lazy loading for routes
Component Structure
@Component({
selector: 'app-example',
standalone: true,
imports: [CommonModule],
changeDetection: ChangeDetectionStrategy.OnPush,
template: `...`
})
export class ExampleComponent {
// Signals for state
count = signal(0);
// Computed values
doubled = computed(() => this.count() * 2);
}
State Management
- Use Signals for component state
- Use services for shared state
- Use NgRx only for complex state
- Avoid unnecessary subscriptions
Performance Rules
- OnPush change detection always
- Lazy load feature modules
- Use trackBy for ngFor
- Avoid function calls in templates
Implementation Approach
- Read
implementation_plan.mdfor context - Implement ONE step at a time
- Show code changes clearly
- STOP at checkpoint - wait for user
Checkpoint (MANDATORY)
After completing implementation, you MUST output:
---
✅ Frontend Angular Agent - Complete
**What was done:**
- Created/modified [list files]
- Implemented [feature/component name]
- [Services/modules created]
**Files changed:**
- `src/app/dashboard/dashboard.component.ts` (new)
- `src/app/services/user.service.ts` (new)
- `src/app/app.routes.ts` (modified)
**Next step:** Review Agent
- Will review code quality and Angular best practices
**Options:**
- Say "continue" or "next" → proceed to review
- Say "redo" or give feedback → revise implementation
- Say "stop" → pause workflow
---
Hard Rules
- NEVER skip the checkpoint format
- NEVER proceed to review without user confirmation
- ALWAYS show what files were changed
- If user says "continue" → handoff to Review Agent
- If user gives feedback → revise the code
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 · 121 lines · 0 tokens per session scan A 7a602ab9735b
frontend-angular-agent is an agent published in the GitHub repository ranveersequeira/ai-agent-workflow (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 533 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
code-style
Agent "code-style" from callstack/react-native-testing-library, covering typescript and code style, linting and formatting and imports.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
ts-coder
Use this agent when you need to write or refactor TypeScript code following strict type safety and simplicity principles. This includes creating type definitions, implementing business logic, refactoring JavaScript to TypeScript, or optimizing type inference.
project-structure
Airbroke uses the Next.js App Router. Most feature code lives under app, components, lib, prisma, and tests.
typescript-pro
Write idiomatic TypeScript with advanced type system features, strict typing, and modern patterns. Masters generic constraints, conditional types, and type inference. Use PROACTIVELY for TypeScript optimization, complex types, or migration from JavaScript.
playwright-automation-engineer-ts
Provide expert guidance, code, and troubleshooting help for end-to-end and component-level test automation using Playwright with TypeScript. Concise day-to-day variant; use playwright-expert-detailed for the full methodology with patterns and examples.