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/cuongtl1992/vibe-skills/angular-componentnpx skills add cuongtl1992/vibe-skills --skill angular-componentgit 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-component)<a href="https://agentmods.dev/skills/cuongtl1992/vibe-skills/angular-component"><img src="https://agentmods.dev/badge/skills/cuongtl1992/vibe-skills/angular-component.svg" alt="Measured on agentmods" 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 | $0.00065 | $0.00868 |
| Opus 5 | $0.00032 | $0.00434 |
| Sonnet 5 | $0.00013 | $0.00174 |
| Haiku 4.5 | $0.00006 | $0.00087 |
Grade A, and why
angular-component 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 5d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular Component Patterns
Component Declaration
Components are standalone by default in Angular 17+. Do NOT set standalone: true.
@Component({
selector: 'app-entity-list',
imports: [CommonModule, RouterModule],
templateUrl: './entity-list.component.html',
styleUrl: './entity-list.component.scss',
changeDetection: ChangeDetectionStrategy.OnPush,
})
export class EntityListComponent {
// 1. Injected dependencies
private readonly service = inject(EntityService);
private readonly router = inject(Router);
// 2. Signal inputs
readonly entityId = input.required<string>();
readonly status = input<string>('active');
// 3. Signal outputs
readonly selected = output<Entity>();
// 4. Signals for reactive state
readonly items = signal<Entity[]>([]);
readonly loading = signal(false);
// 5. Computed values
readonly filteredItems = computed(() =>
this.items().filter(i => this.status() === 'all' || i.status === this.status())
);
}
Signal Inputs (not @Input)
// Required input
readonly entityId = input.required<number>();
// Optional with default
readonly pageSize = input(20);
// Transform
readonly id = input(0, { transform: numberAttribute });
// Alias
readonly label = input('', { alias: 'buttonLabel' });
Signal Outputs (not @Output)
readonly selected = output<Entity>();
readonly closed = output<void>();
// Emit
this.selected.emit(entity);
this.closed.emit();
View Queries (not @ViewChild)
readonly nameInput = viewChild<ElementRef<HTMLInputElement>>('nameInput');
readonly items = viewChildren(ItemComponent);
// Usage
this.nameInput()?.nativeElement.focus();
Control Flow (not *ngIf/*ngFor)
@if (loading()) {
<app-spinner />
} @else if (error()) {
<app-error [message]="error()" />
} @else {
@for (item of items(); track item.id) {
<app-item [data]="item" (click)="onSelect(item)" />
} @empty {
<p>No items found</p>
}
}
@switch (status()) {
@case ('active') { <span class="badge-active">Active</span> }
@case ('inactive') { <span class="badge-inactive">Inactive</span> }
@default { <span>Unknown</span> }
}
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.
- 5d ago First seen · 141 lines · 65 tokens per session scan A 206940911b64
angular-component is a skill published in the GitHub repository cuongtl1992/vibe-skills (10 stars, last pushed 5mo ago), licensed MIT. It adds 65 tokens to every session and 868 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…