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/agenticpawan/fullstack-pilot/angular-lint-governancenpx skills add AgenticPawan/FullStack-Pilot --skill angular-lint-governancegit clone --depth 1 https://github.com/AgenticPawan/FullStack-PilotWhat 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.00102 | $0.02769 |
| Opus 5 | $0.00051 | $0.01385 |
| Sonnet 5 | $0.00020 | $0.00554 |
| Haiku 4.5 | $0.00010 | $0.00277 |
Grade A, and why
angular-lint-governance 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standard IDs
| ID | Severity | What it checks |
|---|---|---|
| LNT-001 | P1 | ESLint configured locally/IDE-only, not run as a required CI gate |
| LNT-002 | P1 | No @angular-eslint/* template rules — .html files skipped entirely |
| LNT-003 | P2 | ESLint and Prettier rules conflict — no eslint-config-prettier |
| LNT-004 | P2 | No pre-commit hook (husky + lint-staged) catching errors before CI |
| LNT-005 | P1 | Blanket file-level eslint-disable instead of scoped, justified, line-level disables |
| LNT-006 | P2 | No documented severity policy distinguishing warnings from must-fix errors |
Cross-reference: angular-upgrade-path owns the one-time migration from TSLint to ESLint
(schematics, config translation, tslint.json removal). This skill governs the ongoing
enforcement of the ESLint setup once it exists — CI gating, template linting, Prettier
integration, pre-commit hooks, and disable-comment discipline.
Check A — ESLint as a required CI gate (LNT-001)
Detection
- Confirm
package.jsonhas anng lint/eslint .script. - Search CI workflow files (
.github/workflows/*.yml, Azure Pipelines YAML) for a step that runs the lint script. - If the lint step exists but is not in the required-checks list for the branch-protection rule
(or runs with
continue-on-error: true/|| true), flag it — a lint failure must block merge, not just print a warning in the log. - If no CI lint step exists at all, flag LNT-001 as the primary finding — linting only happening
in a developer's IDE means violations reach
mainunchecked.
BAD — lint step present but failure is swallowed
# .github/workflows/ci.yml
- name: Lint
run: npm run lint || true # non-zero exit is silently ignored — never blocks the PR
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 · 275 lines · 102 tokens per session scan A a0998dda2fc6
angular-lint-governance is a skill published in the GitHub repository AgenticPawan/FullStack-Pilot (2 stars, last pushed 1mo ago), licensed MIT. It adds 102 tokens to every session and 2,769 once invoked, about $0.0005 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
reference-signal-forms
Explains the mental model and architecture of the code under packages/forms/signals. You MUST use this skill any time you plan to work with code in packages/forms/signals.
roll-dice
Roll dice using a random number generator. Use when asked to roll a die (d6, d20, etc.), roll dice, or generate a random dice roll.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
run-tests
Run project tests using Maven (mvn). Use when the user asks to run tests.