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-ngrx-statenpx skills add AgenticPawan/FullStack-Pilot --skill angular-ngrx-stategit 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.00120 | $0.02286 |
| Opus 5 | $0.00060 | $0.01143 |
| Sonnet 5 | $0.00024 | $0.00457 |
| Haiku 4.5 | $0.00012 | $0.00229 |
Grade A, and why
angular-ngrx-state 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standard IDs
| ID | Severity | What it checks |
|---|---|---|
| NGRX-001 | P2 | Full NgRx boilerplate used for simple local component state that a signal would handle |
| NGRX-002 | P1 | Selectors not memoized via createSelector, recomputing on every store emission |
| NGRX-003 | P0 | Effect with no catchError, silently killing the entire effects stream on error |
| NGRX-004 | P1 | Component subscribes to the store directly instead of async pipe or toSignal() |
| NGRX-005 | P2 | Feature state registered eagerly at root instead of lazy-loaded via provideState |
| NGRX-006 | P2 | No documented policy for teams running NgRx and Signals side by side |
Check A — Full NgRx boilerplate for simple local state (NGRX-001)
Detection
Check whether a new feature adds an action, reducer, effect, and selector purely to hold
state that only one component (or a small subtree) cares about — a dropdown's open/closed
state, a form's dirty flag, a modal's visibility. This ceremony (four+ files, action-type
strings, dispatch boilerplate) buys nothing over a local signal() when nothing outside the
component tree needs to read or react to that state. Reserve NgRx for state that is genuinely
cross-cutting, shared across distant parts of the tree, or needs time-travel debugging. See
angular-signals-and-state for the local-state-first guidance this complements.
BAD — NgRx boilerplate for a component-local toggle
// actions
export const togglePanel = createAction('[Settings] Toggle Panel');
// reducer
export const settingsReducer = createReducer(
initialState,
on(togglePanel, state => ({ ...state, panelOpen: !state.panelOpen }))
);
// selector
export const selectPanelOpen = createSelector(selectSettingsState, s => s.panelOpen);
// component — dispatches/selects the store for a value nothing else uses
export class SettingsComponent {
private store = inject(Store);
panelOpen = this.store.selectSignal(selectPanelOpen);
toggle() { this.store.dispatch(togglePanel()); }
}
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 · 275 lines · 120 tokens per session scan A 31429d88d68d
angular-ngrx-state is a skill published in the GitHub repository AgenticPawan/FullStack-Pilot (2 stars, last pushed 1mo ago), licensed MIT. It adds 120 tokens to every session and 2,286 once invoked, about $0.0006 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…