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 cuongtl1992/vibe-skills --skill angular-devgit clone --depth 1 https://github.com/cuongtl1992/vibe-skillsWrote 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/cuongtl1992/vibe-skills/angular-dev)<a href="https://agentmods.dev/skills/cuongtl1992/vibe-skills/angular-dev"><img src="https://agentmods.dev/badge/skills/cuongtl1992/vibe-skills/angular-dev/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/cuongtl1992/vibe-skills/angular-dev"><img src="https://agentmods.dev/badge/skills/cuongtl1992/vibe-skills/angular-dev.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.00134 | $0.01502 |
| Opus 5.5 | $0.00054 | $0.00601 |
| Sonnet 5.5 | $0.00027 | $0.00300 |
| Haiku 4.5 | $0.00013 | $0.00150 |
Grade A, and why
angular-dev 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular Dev
Angular 17+ development guide — Standalone Components, Signals, NgRx, and .NET backend integration.
Stack assumptions
- Angular 17+ — Standalone Components (no NgModules by default)
- State: Signals for local/simple state, NgRx Signal Store for feature state
- HTTP:
HttpClientwith typed responses, interceptors for auth - Backend: .NET Web API (RESTful, likely following BE CQRS pattern)
- Styling: SCSS, standalone imports
- Testing: Jest (or Jasmine) + Angular Testing Library
Quick reference — when to read which file
| Task | Read |
|---|---|
| Build components, templates, directives | references/component-patterns.md |
| NgRx Signal Store, Signals, state design | references/state-management.md |
| HTTP service, interceptors, .NET integration | references/backend-integration.md |
Core principles
1. Standalone-first
Always generate standalone components unless user explicitly requests NgModule.
@Component({
selector: 'app-product-list',
standalone: true,
imports: [CommonModule, RouterModule],
templateUrl: './product-list.component.html',
})
export class ProductListComponent { }
2. Signals for local state
Use signal() and computed() instead of class properties + manual change detection.
export class CartComponent {
items = signal<CartItem[]>([]);
total = computed(() => this.items().reduce((s, i) => s + i.price, 0));
addItem(item: CartItem) {
this.items.update(current => [...current, item]);
}
}
3. Typed HTTP — always
Every API call must have a typed response interface matching the .NET DTO.
// ✅ typed
this.http.get<ProductDto[]>('/api/products')
// ❌ avoid
this.http.get<any>('/api/products')
4. Inject function over constructor DI
// ✅ Angular 17+ style
export class ProductService {
private http = inject(HttpClient);
private store = inject(ProductStore);
}
Feature structure (lazy-loaded)
What ships with it
3 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.
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 · 222 lines · 134 tokens per session scan A b0e347424742
angular-dev is a skill published in the GitHub repository cuongtl1992/vibe-skills (11 stars, last pushed 7mo ago), licensed MIT. It adds 134 tokens to every session and 1,502 once invoked, about $0.0005 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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.