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/arroyo-gonzalo/codex-devkit/angular-featurenpx skills add Arroyo-Gonzalo/codex-devkit --skill angular-featuregit clone --depth 1 https://github.com/Arroyo-Gonzalo/codex-devkitWhat 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.00042 | $0.00602 |
| Opus 5 | $0.00021 | $0.00301 |
| Sonnet 5 | $0.00008 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
angular-feature 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular Feature
Purpose
Implement frontend functionality that integrates naturally with the existing Angular application.
Prioritize consistency with the existing architecture over introducing new patterns.
Workflow
1. Understand the request
Identify:
- business objective;
- expected user behavior;
- affected pages;
- affected components;
- routing impact;
- API dependencies;
- validation requirements;
- authorization requirements.
Do not begin implementation until the expected behavior is clear.
2. Inspect the repository
Inspect:
- similar components;
- routing structure;
- services;
- shared components;
- state management;
- interceptors;
- guards;
- styling conventions;
- existing forms.
Reuse existing patterns whenever possible.
3. Design the change
Determine:
- required components;
- required services;
- routing updates;
- forms;
- validation;
- API integration;
- loading states;
- error handling;
- empty states.
Avoid introducing unnecessary components.
4. Implement
Keep responsibilities clear.
Components should:
- render the UI;
- handle user interaction;
- delegate business operations.
Services should:
- communicate with APIs;
- centralize reusable logic;
- avoid UI responsibilities.
Keep presentation and business logic separated.
5. User experience
Ensure:
- loading indicators;
- empty states;
- error states;
- success feedback;
- responsive layouts;
- accessibility.
Avoid blocking the UI unnecessarily.
6. Validation
Verify:
- routing;
- navigation;
- forms;
- validation;
- API communication;
- error handling;
- typing consistency.
Avoid introducing breaking frontend behavior.
7. Tests
When practical:
- update existing tests;
- add focused component or service tests;
- verify regression coverage.
Avoid testing framework internals.
8. Review
Inspect the final implementation.
Verify:
- consistency;
- duplicated logic;
- unused imports;
- dead code;
- naming consistency;
- unnecessary state duplication.
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 · 171 lines · 42 tokens per session scan A 970d38795288
angular-feature is a skill published in the GitHub repository Arroyo-Gonzalo/codex-devkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 602 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
general-video
Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated…
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
mintlify-preview
Run the public Mintlify product docs site locally for live preview. Use when previewing or iterating on docs under docs/ (.mdx/.md pages, docs.json nav), or when the user says "start the docs", "run mintlify", "preview the docs site".