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.01001 |
| Opus 5.5 | $0.00023 | $0.00400 |
| Sonnet 5.5 | $0.00011 | $0.00200 |
| Haiku 4.5 | $0.00006 | $0.00100 |
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 1mo 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 — 91 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
- Docs chrome:
src/app/docs/layout/,src/app/docs/ui/(DocsExample,DocsSnippet,DocsPager,DocsToc) - 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.
- Prefer shadcn-style information flow when rewriting a page:
- one-line lead under the H1,
- hero live example before Installation,
- Installation (Command / Manual) then Usage as compact snippets,
- one H2 per capability (not a dump under “Examples”),
- preview code must match the live example exactly.
- Build examples with
app-docs-example(single canvas, not nestedapp-preview):- toolbar is an
el-segmented-buttonwith preview / code / standards icon items, - preview: live component output only (no shadcn-style “View Code” peek for now),
- code: the exact markup for that preview,
- standards: short UX/a11y rationale via
<ng-template #standards>.
- toolbar is an
- Give every docs
h2a stable slugid(e.g.id="installation") so the right-rail On this page TOC can link and scroll-spy correctly. The layout auto-slugs missing ids, but explicit ids are preferred. - Style docs chrome and page helpers with BEM (
docs-block,docs-block__element,docs-block--modifier). No bare.is-active/ one-off utilities; see.cursor/rules/bem-scss.mdcand component conventions. - 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.
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.
- 1mo ago Changed · +22 lines 5e7f9ce0bd4e
- 1mo 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 3d ago), licensed MIT. It adds 57 tokens to every session and 1,001 once invoked, about $0.0002 per session on Opus 5.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-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…
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/.
getting-started
Connect Taskade and show the user what they can do with it. Use when the user says "set up Taskade", "connect Taskade", "what can you do in Taskade", "what is in my Taskade workspace", or when a Taskade tool fails with a sign-in or plan error.
backup-my-app
Copy a Taskade Genesis app (app source, projects, agents and automation definitions) into a local folder as readable files, for a backup, a handover to a client, or a README. Use when the user says "back up my Taskade app", "export my app", "download my app source", "save a copy of my workspace", or "document my app".
stockbit-auth
Log in to Stockbit and capture the session for this server — opens the browser login flow and verifies the token was stored. Use when the user asks to log in or re-authenticate to Stockbit, or after a status check reports the session expired, HTTP 401, or logged out.