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-httpnpx skills add cuongtl1992/vibe-skills --skill angular-httpgit 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-http)<a href="https://agentmods.dev/skills/cuongtl1992/vibe-skills/angular-http"><img src="https://agentmods.dev/badge/skills/cuongtl1992/vibe-skills/angular-http.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.00047 | $0.00669 |
| Opus 5 | $0.00023 | $0.00334 |
| Sonnet 5 | $0.00009 | $0.00134 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
angular-http 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 3d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular HTTP Patterns
Two-layer pattern: API Client (Observable) → Repository (Result).
API Client Layer
Returns Observable<DTO> — no Result wrapping here:
import { HttpClient, HttpParams } from '@angular/common/http';
import { Injectable, inject } from '@angular/core';
import { Observable, catchError, throwError } from 'rxjs';
@Injectable()
export class EntityApiClient {
private readonly http = inject(HttpClient);
private readonly baseUrl = inject(API_BASE_URL);
findAll(params?: HttpParams): Observable<EntityListResponse> {
return this.http.get<EntityListResponse>(
`${this.baseUrl}/entities`, { params }
).pipe(
catchError(error => throwError(() => new Error(this.extractError(error))))
);
}
create(payload: CreateEntityRequest): Observable<EntityResponse> {
return this.http.post<EntityResponse>(
`${this.baseUrl}/entities`, payload
).pipe(
catchError(error => throwError(() => new Error(this.extractError(error))))
);
}
private extractError(error: unknown): string {
if (error instanceof Error) return error.message;
if (typeof error === 'object' && error !== null && 'error' in error) {
const httpError = error as { error?: { message?: string } };
return httpError.error?.message ?? 'Request failed';
}
return 'Unknown error';
}
}
Repository Layer
Wraps API calls with Result<T> using firstValueFrom:
import { firstValueFrom } from 'rxjs';
@Injectable()
export class EntityRepositoryImpl implements EntityRepository {
private readonly apiClient = inject(EntityApiClient);
async find(params: FilterParams): Promise<Result<PagedResult<Entity>>> {
try {
const response = await firstValueFrom(this.apiClient.findAll(this.buildParams(params)));
return Result.success({
data: response.data.map(EntityMapper.toDomain),
total: response.total,
});
} catch (error: unknown) {
return Result.failure(error instanceof Error ? error.message : 'Unknown error');
}
}
async create(params: CreateEntityParams): Promise<Result<Entity>> {
try {
const response = await firstValueFrom(
this.apiClient.create(EntityMapper.toCreateDto(params))
);
return Result.success(EntityMapper.toDomain(response.data));
} catch (error: unknown) {
return Result.failure(error instanceof Error ? error.message : 'Failed to create');
}
}
}
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.
- 3d ago First seen · 96 lines · 47 tokens per session scan A f3c28e5b60d4
angular-http is a skill published in the GitHub repository cuongtl1992/vibe-skills (10 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 669 once invoked, about $0.0002 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…