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 skills add Nevaberry/nevaberry-plugins --skill angular-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWrote 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/skills/nevaberry/nevaberry-plugins/angular-knowledge-patch)<a href="https://agentmods.dev/skills/nevaberry/nevaberry-plugins/angular-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/angular-knowledge-patch/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/skills/nevaberry/nevaberry-plugins/angular-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/angular-knowledge-patch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00007 | $0.02081 |
| Opus 5.5 | $0.00003 | $0.00832 |
| Sonnet 5.5 | $0.00001 | $0.00416 |
| Haiku 4.5 | $0.00001 | $0.00208 |
Grade A, and why
angular-knowledge-patch 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular Knowledge Patch
Use this skill when writing, reviewing, upgrading, or debugging a modern Angular application. Read the breaking changes and defaults first, then open the topic reference that matches the work.
Reference index
| Reference | Topics |
|---|---|
| Compatibility, security, and releases | Node.js, TypeScript, RxJS, browsers, support policy, migrations, CSP, sanitization, and i18n security |
| Core reactivity | Resources, effects, runtime bindings, zoneless change detection, services, signals, and HTTP behavior |
| Signal Forms | Field trees, schemas, validation, submission, custom controls, and Material or Aria integration |
| SSR, hydration, and routing | Hybrid rendering, server routes, incremental hydration, pending work, transfer cache, engines, and router lifecycle |
| Templates and animations | Template syntax, diagnostics, CSS enter and leave animation, defer triggers, and host-directive matching |
| Testing and tooling | Vitest, migrations, HMR, compiler checks, CLI tools, build changes, and removed test APIs |
| UI, platform, and DevTools | Angular Aria, Material, CDK, locale data, profiling, and debugging visualizations |
Breaking changes and defaults
Components default to OnPush
An omitted changeDetection now means OnPush. Use the renamed eager strategy only for a component that truly requires full eager checking:
@Component({
selector: 'legacy-widget',
template: `...`,
changeDetection: ChangeDetectionStrategy.Eager,
})
export class LegacyWidget {}
Audit code that mutates plain fields without a recognized notification. Prefer signals, markForCheck(), ComponentRef.setInput(), template or host listeners, or attachment of an already-dirty view.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- coverage.json 1.7 KB
- references/compatibility-security-and-releases.md 4.9 KB
- references/core-reactivity.md 8.7 KB
- references/signal-forms.md 6.5 KB
- references/ssr-hydration-and-routing.md 6.3 KB
- references/templates-and-animations.md 4.8 KB
- references/testing-and-tooling.md 6.2 KB
- references/ui-platform-and-devtools.md 4.2 KB
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 · 186 lines · 7 tokens per session scan A 05f57d097901
angular-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (23 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 2,081 once invoked, about $0.0000 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-30.
Other skills, from other repositories
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.clientCapabilities, ctx.enrich, ctx.content), and when to use each.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
polish-docs-meta
Finalize documentation and project metadata for a ship-ready MCP server. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…