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-module-setupgit 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-module-setup)<a href="https://agentmods.dev/skills/cuongtl1992/vibe-skills/angular-module-setup"><img src="https://agentmods.dev/badge/skills/cuongtl1992/vibe-skills/angular-module-setup/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-module-setup"><img src="https://agentmods.dev/badge/skills/cuongtl1992/vibe-skills/angular-module-setup.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.00063 | $0.00686 |
| Opus 5.5 | $0.00025 | $0.00274 |
| Sonnet 5.5 | $0.00013 | $0.00137 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
angular-module-setup 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular Module Setup — DI + Routing
inject() Function
All DI uses inject() function. Never constructor injection.
private readonly http = inject(HttpClient);
private readonly destroyRef = inject(DestroyRef);
private readonly repository = inject(ENTITY_REPOSITORY);
private readonly dialogControl = inject(DialogControl, { optional: true });
InjectionToken for Repository Ports
Domain layer defines the port + token:
import { InjectionToken } from '@angular/core';
export interface EntityRepository {
find(params: FilterParams): Promise<Result<PagedResult<Entity>>>;
create(params: CreateParams): Promise<Result<Entity>>;
update(params: UpdateParams): Promise<Result<Entity>>;
delete(id: EntityId): Promise<Result<void>>;
}
export const ENTITY_REPOSITORY = new InjectionToken<EntityRepository>('EntityRepository');
Route-Level Providers
Providers registered at route level, NOT component or root:
export const entityRoutes: Routes = [
{
path: '',
loadComponent: () => import('./pages/entity-page.component').then(m => m.EntityPageComponent),
providers: [...EntityInfrastructureProviders],
},
];
Infrastructure Providers Array
export const EntityInfrastructureProviders: Provider[] = [
// Queries (Application Layer)
GetEntitiesQuery,
// Use Cases (Application Layer)
CreateEntityUseCase, UpdateEntityUseCase, DeleteEntityUseCase,
// API Clients (Infrastructure Layer)
EntityApiClient,
// Repository Implementations (Adapters)
{ provide: ENTITY_REPOSITORY, useClass: EntityRepositoryImpl },
];
Order: Queries → UseCases → API Clients → Repository implementations
Lazy Loading
// Single component
{ path: 'entities', loadComponent: () => import('@app/entity').then(m => m.EntityPageComponent) }
// Child routes with shared providers
{ path: 'entities', loadChildren: () => import('@app/entity').then(m => m.entityRoutes) }
Route Params as Signal Inputs
What ships with it
1 file 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 · 117 lines · 63 tokens per session scan A 7292527a8dff
angular-module-setup is a skill published in the GitHub repository cuongtl1992/vibe-skills (11 stars, last pushed 7mo ago), licensed MIT. It adds 63 tokens to every session and 686 once invoked, about $0.0003 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.