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 skills/agenticpawan/fullstack-pilot/angular-runtime-confignpx skills add AgenticPawan/FullStack-Pilot --skill angular-runtime-configgit clone --depth 1 https://github.com/AgenticPawan/FullStack-PilotWhat 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.00095 | $0.02966 |
| Opus 5 | $0.00048 | $0.01483 |
| Sonnet 5 | $0.00019 | $0.00593 |
| Haiku 4.5 | $0.00010 | $0.00297 |
Grade A, and why
angular-runtime-config 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standard IDs
| ID | Severity | What it checks |
|---|---|---|
| ARC-001 | P1 | API base URL / feature flags baked into environment.ts at build time |
| ARC-002 | P1 | No runtime config.json + APP_INITIALIZER/provideAppInitializer pattern |
| ARC-003 | P1 | Runtime config not cached synchronously before early-bootstrap code needs it |
| ARC-004 | P0 | Secrets or sensitive values placed in the client-visible config.json |
| ARC-005 | P1 | No fallback/error handling when the config endpoint is unreachable at startup |
| ARC-006 | P2 | Inconsistent precedence between build-time defaults and runtime overrides |
Cross-reference: this is the Angular-side counterpart to dotnet-dynamic-configuration —
that skill governs the backend's layered configuration providers (appsettings + environment
variables + Azure App Configuration); this skill governs how the same promoted container image
picks up environment-specific values on the client without a rebuild.
Check A — Build-time config forces per-environment images (ARC-001)
Detection
- Inspect
src/environments/environment.ts/environment.prod.ts(orfileReplacementsinangular.json) forapiBaseUrl, feature-flag booleans, or tenant-specific values. - Confirm whether the Dockerfile/CI pipeline builds a distinct image per environment
(
ng build --configuration=staging,ng build --configuration=production) rather than building once and promoting the same artifact through environments. - Flag any environment-specific value that only exists as a compiled-in TypeScript constant — changing it requires a rebuild, which breaks "build once, deploy everywhere" and makes the staging-tested image different from the production image.
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 · 311 lines · 95 tokens per session scan A b89482b9a372
angular-runtime-config is a skill published in the GitHub repository AgenticPawan/FullStack-Pilot (2 stars, last pushed 1mo ago), licensed MIT. It adds 95 tokens to every session and 2,966 once invoked, about $0.0005 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 skills, from other repositories
azure-mgmt-apicenter-dotnet
Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery. Use for creating API services, workspaces, APIs, versions, definitions, environments, deployments, and metadata schemas. Triggers: "API Center", "ApiCenterService", "ApiCenterWorkspace", "ApiCenterApi", "API…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
azure-communication-chat-java
Build real-time chat applications with Azure Communication Services Chat Java SDK. Use when implementing chat threads, messaging, participants, read receipts, typing notifications, or real-time chat features.
union-type-wrappers
Add typed getters and setters over BinaryData properties that represent TypeSpec union types in generated Java models. Use when generated classes expose BinaryData for union-typed fields and you need ergonomic, type-safe accessors instead.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…