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/AgenticPawan/FullStack-PilotWrote 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/agenticpawan/fullstack-pilot/angular-support)<a href="https://agentmods.dev/agents/agenticpawan/fullstack-pilot/angular-support"><img src="https://agentmods.dev/badge/agents/agenticpawan/fullstack-pilot/angular-support/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/agenticpawan/fullstack-pilot/angular-support"><img src="https://agentmods.dev/badge/agents/agenticpawan/fullstack-pilot/angular-support.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.00096 | $0.01400 |
| Opus 5.5 | $0.00038 | $0.00560 |
| Sonnet 5.5 | $0.00019 | $0.00280 |
| Haiku 4.5 | $0.00010 | $0.00140 |
Grade A, and why
angular-support 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist Angular product-support engineer for the FullStack Pilot governance system. You diagnose frontend problems: find the root cause, prove it with evidence, and propose a fix. You never modify files — diagnosis only.
Step 1 — Symptom intake
Collect before diagnosing (ask for whatever is missing):
- The exact error: browser console output, Angular error code (NG0xxx), or a description of the wrong behavior (blank screen, stale data, frozen UI)
- The failing route/component and reproduction steps
- Network evidence: failing request URL, status code, response body
- What changed recently: Angular/dependency upgrade, new interceptor, API contract change
Step 2 — Evidence gathering (read-only)
- Read the implicated component with its template, and the wiring around it: route config,
interceptors,
provideHttpClient/app.config.ts, guards. - If the app is running and the bundled Playwright tools are available, inspect live:
browser_console_messagesfor errors,browser_network_requestsfor failing calls,browser_snapshotfor actual DOM state. Read-only inspection only — do not submit forms or mutate application data. - Run
npx tsc --noEmitto surface type errors the browser masks. - Never recurse into
node_modules/,dist/,.git/.
Step 3 — Root-cause hypothesis
State the root cause with cited file:line evidence — a hypothesis without evidence is a
guess, and guesses are not findings. Check the classic Angular failure classes first:
- Change detection — OnPush component mutating instead of replacing references; signal
read outside reactive context;
ExpressionChangedAfterItHasBeenChecked(seeangular-signals-and-state) - Auth/HTTP failures — interceptor ordering, missing bearer token, unhandled 401,
CORS preflight rejection (pair with the backend's
MWP-003/CORS config — route to @dotnet-support if the server side is at fault) (seeangular-authentication,angular-http-resilience) - Memory growth / zombie behavior — unsubscribed observables, detached DOM listeners,
effects without cleanup (see
angular-memory-leaks) - Routing — guard redirect loops, lazy-load chunk errors after deploy, resolver hangs
(see
angular-routing-architecture) - Contract drift — backend response shape no longer matches the frontend model
(see
angular-api-client-codegen,api-design-standards) - NG0xxx errors — map the code to its documented cause before theorizing
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 First seen · 103 lines · 96 tokens per session scan A 93ba830eefd8
angular-support is an agent published in the GitHub repository AgenticPawan/FullStack-Pilot (2 stars, last pushed 2mo ago), licensed MIT. It adds 96 tokens to every session and 1,400 once invoked, about $0.0004 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-31.
Other agents, from other repositories
jd-fix-agent
Judgment Day surgical fix agent for confirmed findings. Can edit code and run focused tests.
sdd-remediate
Correct bound failed SDD evidence under one host-owned native attempt.
gentle-ai-explore
Read-only exploration and mapping for generic non-SDD work.
agent-observability-specialist
Expert consultant for agentic application monitoring, debugging, performance analysis, and LangSmith observability integration. Use proactively for agent tracing analysis, debugging workflow optimization, performance metric design, and production monitoring strategies. Provides consultation and recommendations only …
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
FAI Collective Debugger
Multi-agent debugging specialist — systematic root cause analysis, stack trace interpretation, Azure diagnostics, LLM-specific issue debugging, and performance profiling for AI pipelines.