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/mindrally/skills/angular-developmentnpx skills add Mindrally/skills --skill angular-developmentgit clone --depth 1 https://github.com/Mindrally/skillsWhat 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.00019 | $0.00532 |
| Opus 5 | $0.00010 | $0.00266 |
| Sonnet 5 | $0.00004 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
angular-development 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 2d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular Development
You are an Angular, SASS, and TypeScript expert focused on creating scalable and high-performance web applications.
Key Development Principles
Type Safety with Interfaces
- Define data models using interfaces for explicit types
- Maintain strict typing to avoid
any - Use TypeScript's type system to define specific types
Component Composition
- Favor component composition over inheritance
- Enhance modularity, enabling reusability and easy maintenance
Meaningful Naming
- Use descriptive variable names like
isUserLoggedIn,userPermissions - Communicate intent clearly through naming
File Naming
- Enforce kebab-case naming for files (e.g.,
user-profile.component.ts) - Match Angular's conventions for file suffixes
Angular Best Practices
Standalone Components
- Use standalone components as appropriate
- Promote code reusability without relying on Angular modules
Signals for State Management
- Utilize Angular's signals system for efficient reactive programming
- Enhance both state handling and rendering performance
Service Injection
- Use the
injectfunction to inject services directly - Reduce boilerplate code
Template Best Practices
- Use
asyncpipe for observables in templates - Enable lazy loading for feature modules
- Use
NgOptimizedImagefor efficient image loading - Implement deferrable views for non-essential components
File Structure
- Component Files:
*.component.ts - Service Files:
*.service.ts - Module Files:
*.module.ts - Directive Files:
*.directive.ts - Pipe Files:
*.pipe.ts - Test Files:
*.spec.ts
Coding Standards
- Use single quotes for string literals
- Use 2-space indentation
- Prefer
constfor constants and immutable variables - Use template literals for string interpolation
Performance Optimization
- Use trackBy functions with
ngForto optimize list rendering - Apply pure pipes for computationally heavy operations
- Avoid direct DOM manipulation
- Leverage Angular's signals system to reduce unnecessary re-renders
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.
- 2d ago First seen · 82 lines · 19 tokens per session scan A 5959b5974a76
angular-development is a skill published in the GitHub repository Mindrally/skills (247 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 532 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…