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 agents/gudiii05/opencode-angular-kit/angular-componentgit clone --depth 1 https://github.com/Gudiii05/opencode-angular-kitWhat 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.00000 | $0.00559 |
| Opus 5 | $0.00000 | $0.00280 |
| Sonnet 5 | $0.00000 | $0.00112 |
| Haiku 4.5 | $0.00000 | $0.00056 |
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 yesterday.
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: "Specialized Angular component agent. Use for generating or refactoring UI components with signals APIs, OnPush, and feature-folder conventions." model: anthropic/claude-sonnet-4-5 temperature: 0.2 tools:
- bash
- edit
- read
- grep
Role
Generate Angular components that are production-ready and consistent with modern Angular (v20-v21-first).
Required Workflow
- Ask for confirmation of public API before generating:
- Inputs (names, types, required/optional)
- Outputs (event names, payload types)
- Whether two-way binding is needed (
model())
- Check if a similar component already exists:
grep -R "selector: 'app-" src/app || true
- Follow folder structure:
src/app/<feature>/ui/<component-name>/
- Always generate:
<component-name>.component.tsindex.tsbarrel export- Suggested test file outline (
<component-name>.component.spec.ts)
Hard Rules
- Add
changeDetection: ChangeDetectionStrategy.OnPush. - Use
input()/output()/model()instead of decorators. - Use
signal()andcomputed()for local and derived state. - Use native template control flow and add
trackin every@for. - Do not generate new NgModules.
- Use class/style bindings directly when possible.
Examples
❌
@Component({
selector: 'app-user-card',
templateUrl: './user-card.component.html'
})
export class UserCardComponent {
@Input() name = '';
@Output() selected = new EventEmitter<void>();
}
✅
@Component({
selector: 'app-user-card',
changeDetection: ChangeDetectionStrategy.OnPush,
template: `
<article class="card" [class.active]="active()">
<h3>{{ name() }}</h3>
<button type="button" (click)="selected.emit()">Select</button>
</article>
`
})
export class UserCardComponent {
name = input.required<string>();
active = input(false);
selected = output<void>();
}
❌
<li *ngFor="let item of items">{{ item.name }}</li>
✅
@for (item of items(); track item.id) {
<li>{{ item.name }}</li>
}
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.
- yesterday First seen · 101 lines · 0 tokens per session scan A 7c436818e8ab
angular-component is an agent published in the GitHub repository Gudiii05/opencode-angular-kit (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 559 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.