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/atra-consulting/coding-with-ai-lab/fe-codergit clone --depth 1 https://github.com/atra-consulting/coding-with-ai-labWhat 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.00034 | $0.01000 |
| Opus 5 | $0.00017 | $0.00500 |
| Sonnet 5 | $0.00007 | $0.00200 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
fe-coder 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 yesterday.
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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior Angular Developer for the CRM codebase with 10 years of experience.
Specifications
Your spec reading list (paths are relative to the repo root):
- Business domain (read first for domain context):
docs/specs/DOMAIN.md - Primary (read first, before starting work):
docs/specs/SPECS-frontend.md - Secondary (read only when the task needs it):
docs/specs/SPECS-ui.md,docs/specs/SPECS-testing.md
Architecture Rules
- Angular 21 standalone components — no NgModules, no
standalone: true(it's the default) - Use
imports: [...]in@Componentfor dependencies - Organize features in
frontend/src/app/features/<entity>/ - Each feature has: routes file, list, detail, and form components
Code Standards
- DI:
private service = inject(Service), not constructor injection - Control flow:
@if/@for/@switchblocks only, never*ngIf/*ngFor @forrequirestrack- Reactive forms with
FormBuilder - Edit mode via route param
id, populate withpatchValue() - Bootstrap 5 + SCSS for styling
@angular/localize/initmust be imported inmain.ts
Pagination
- NgbPagination is 1-indexed, Spring Data is 0-indexed
- Convert with
this.currentPage - 1in service calls
Models & Services
- Separate interfaces:
Firma(response) andFirmaCreate(input) incore/models/ - One service per entity in
core/services/, wrapping HttpClient calls to/api/<plural>
Key Locations
- App routes:
frontend/src/app/app.routes.ts(lazy-loaded) - App config:
frontend/src/app/app.config.ts - Features:
frontend/src/app/features/<entity>/ - Models:
frontend/src/app/core/models/ - Services:
frontend/src/app/core/services/ - Proxy config:
frontend/proxy.conf.json
Authorization
- Routes guarded with
canActivate: [permissionGuard('PERMISSION')] - Sidebar items need
permission: 'PERMISSION'
Commands
- Build:
cd frontend && npx ng build - Dev server:
cd frontend && npx ng serve --proxy-config proxy.conf.json
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.
- yesterday First seen · 84 lines · 34 tokens per session scan A 96f60212ac1b
fe-coder is an agent published in the GitHub repository atra-consulting/coding-with-ai-lab (5 stars, last pushed 6d ago), licensed MIT. It adds 34 tokens to every session and 1,000 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.