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-formsnpx skills add cuongtl1992/vibe-skills --skill angular-formsgit 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-forms)<a href="https://agentmods.dev/skills/cuongtl1992/vibe-skills/angular-forms"><img src="https://agentmods.dev/badge/skills/cuongtl1992/vibe-skills/angular-forms.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.00060 | $0.00700 |
| Opus 5 | $0.00030 | $0.00350 |
| Sonnet 5 | $0.00012 | $0.00140 |
| Haiku 4.5 | $0.00006 | $0.00070 |
Grade A, and why
angular-forms 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 4d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular Reactive Forms
Typed reactive forms with signal-based status tracking, commonly used inside dialog components.
Core Form Setup
import { FormControl, FormGroup, ReactiveFormsModule, Validators } from '@angular/forms';
import { toSignal } from '@angular/core/rxjs-interop';
import { startWith } from 'rxjs';
readonly form = new FormGroup({
name: new FormControl('', {
nonNullable: true,
validators: [Validators.required, Validators.maxLength(255)],
}),
description: new FormControl('', { nonNullable: true }),
isActive: new FormControl(true, { nonNullable: true }),
});
Signal-Based Form Status
// MUST use startWith to capture initial status
private readonly formStatus = toSignal(
this.form.statusChanges.pipe(startWith(this.form.status)),
{ initialValue: this.form.status }
);
readonly saveDisabled = computed(() =>
this.formStatus() !== 'VALID' || this._submitting()
);
Computed Error Messages
readonly nameErrorMessage = computed(() => {
const control = this.form.controls.name;
if (!control.touched) return undefined;
if (control.hasError('required')) return 'Name is required';
if (control.hasError('maxlength')) return 'Name must be 255 characters or less';
return undefined;
});
Submission with exhaustMap
Prevent double-submit using Subject + exhaustMap:
private readonly submitTrigger$ = new Subject<void>();
private readonly destroyRef = inject(DestroyRef);
ngOnInit(): void {
this.submitTrigger$
.pipe(
exhaustMap(() => this.handleSubmission()),
takeUntilDestroyed(this.destroyRef) // MUST pass destroyRef
)
.subscribe();
}
onSubmit(): void {
if (this.form.invalid) { this.markFormAsTouched(); return; }
if (this._submitting()) return;
this.submitTrigger$.next();
}
private markFormAsTouched(): void {
Object.values(this.form.controls).forEach(c => c.markAsTouched());
}
Dual Mode (Create/Edit)
mode = input.required<'create' | 'edit'>();
entity = input<Entity>();
readonly isCreateMode = computed(() => this.mode() === 'create');
ngOnInit(): void {
// ... wire submitTrigger$ ...
if (this.mode() === 'edit') {
const existing = this.entity();
if (existing) {
this.form.patchValue({ name: existing.name, description: existing.description });
}
}
}
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.
- 4d ago First seen · 109 lines · 60 tokens per session scan A 1807505750f5
angular-forms is a skill published in the GitHub repository cuongtl1992/vibe-skills (10 stars, last pushed 5mo ago), licensed MIT. It adds 60 tokens to every session and 700 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…