Borrowing it
Nothing to install: this file belongs to AtulFalle/ng-elemental. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AtulFalle/ng-elemental/master/.cursor/skills/ng-elemental-docs-maintenance/SKILL.mdgit clone --depth 1 https://github.com/AtulFalle/ng-elementalWrote 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/atulfalle/ng-elemental/ng-elemental-docs-maintenance)<a href="https://agentmods.dev/skills/atulfalle/ng-elemental/ng-elemental-docs-maintenance"><img src="https://agentmods.dev/badge/skills/atulfalle/ng-elemental/ng-elemental-docs-maintenance/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/atulfalle/ng-elemental/ng-elemental-docs-maintenance"><img src="https://agentmods.dev/badge/skills/atulfalle/ng-elemental/ng-elemental-docs-maintenance.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00057 | $0.00586 |
| Opus 5 | $0.00028 | $0.00293 |
| Sonnet 5 | $0.00011 | $0.00117 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
ng-elemental-docs-maintenance 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 10d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NgElemental docs maintenance
Use this when updating or removing documentation for any El* component page.
Scope
- Component doc pages in
src/app/docs/pages/*-doc.tsand*-doc.html - Documentation navigation and discoverability:
src/app/docs/nav.tssrc/app/app.routes.tssrc/app/docs/pages/home.html
- API/usage examples and standards explanations
Required workflow
- Identify component and current docs status.
- Update doc page examples, usage, and API props to match component behavior.
- Build examples as a single panel pattern (not separate preview/code sections):
- top-right icon controls in this order: preview, code, standards,
- preview: show live component output,
- code: show the exact code for the visible preview,
- standards: explain relevant UX/a11y decisions for that example.
- Ensure docs include a standards/decision section:
- what standards are used,
- why decisions were made,
- links to references,
- explicit success checks covered.
- Use clear, direct wording and semantic structure. Avoid noisy or repetitive headings.
- For component removal, remove stale references from nav, route, and home lists in the same change.
- Verify docs compile and lint through Nx tasks used by this repo.
Example panel template
Each example panel should provide:
- Preview icon: renders the live component example
- Code icon: shows code matching that exact preview
- Standards icon: concise rationale and standards relevant to that example
Keep this panel pattern consistent across all component docs.
Standards section template
Use this structure in each component docs page:
- Standards used (WCAG/APG/native semantics)
- Why decisions were made (short rationale)
- Success checks covered (clear checklist bullets)
- References (authoritative links)
Removal checklist
- Remove route entry from
src/app/app.routes.ts - Remove nav entry from
src/app/docs/nav.ts - Remove card/link from
src/app/docs/pages/home.html - Delete or deprecate
*-doc.tsand*-doc.html(as requested) - Remove imports no longer used after deletion
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.
- 10d ago First seen · 69 lines · 57 tokens per session scan A dbc833302997
ng-elemental-docs-maintenance is a skill published in the GitHub repository AtulFalle/ng-elemental (2 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 586 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
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…
port-sacred-terminal-ui-to-typescript-cli
Take a React Window.tsx (or any sacred component) and produce a terminal CLI screen written in TypeScript that uses Simulacrum — the sacred CLI framework in scripts/cli/lib/.
port-sacred-terminal-ui-to-react-using-same-conventions
Take a CLI screen written for Simulacrum — the sacred CLI framework (scripts/cli/templates/.ts or scripts/python/templates/.py) — and produce a React component that lives inside components/examples/ (or components/) using only sacred's existing primitives — Window, Card, SimpleTable, ActionButton, RowSpaceBetween…
radix-ng-examples
Index of every documented @radix-ng/primitives example. Use when implementing a UI feature to find a working, copy-paste-ready Angular pattern built on the primitives. Each component has an index doc linking to per-example source shards you can copy-paste.
ingest-gradle-upgrade
Ingests a Gradle wrapper upgrade for this repository: reads the release notes, upgrade guides, and linked documentation for the version upgraded to, then updates this repo's own code/tooling and the shipped Gradle MCP skills (src/main/skills/) so everything stays accurate for that version. Positive Triggers (when to…
authoring-gradle-builds
Authoring and modifying Gradle build logic, including settings, plugins, dependencies, tasks, conventions, and upgrades. Activate when build files or plugins must change; use using-gradle for inspection or execution without build-definition edits.