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 skills add AgenticPawan/FullStack-Pilot --skill angular-visual-regression-testinggit clone --depth 1 https://github.com/AgenticPawan/FullStack-PilotWrote 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/agenticpawan/fullstack-pilot/angular-visual-regression-testing)<a href="https://agentmods.dev/skills/agenticpawan/fullstack-pilot/angular-visual-regression-testing"><img src="https://agentmods.dev/badge/skills/agenticpawan/fullstack-pilot/angular-visual-regression-testing/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/agenticpawan/fullstack-pilot/angular-visual-regression-testing"><img src="https://agentmods.dev/badge/skills/agenticpawan/fullstack-pilot/angular-visual-regression-testing.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.00098 | $0.02287 |
| Opus 5.5 | $0.00039 | $0.00915 |
| Sonnet 5.5 | $0.00020 | $0.00457 |
| Haiku 4.5 | $0.00010 | $0.00229 |
Grade A, and why
angular-visual-regression-testing 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standard IDs
| ID | Severity | What it checks |
|---|---|---|
| VRT-001 | P1 | Shared component library has no Storybook (or equivalent) documenting variants/states |
| VRT-002 | P1 | No visual regression tooling catching unintended pixel-level style changes |
| VRT-003 | P2 | Stories only cover the default/happy-path state, missing loading/error/empty/disabled |
| VRT-004 | P1 | Visual regression baselines auto-accepted in CI with no human review/approval |
| VRT-005 | P2 | Theme variants (light/dark/brand) not covered by visual regression snapshots |
| VRT-006 | P0 | No CI gate blocking merge on an unreviewed visual diff for shared-library components |
angular-shared-libraries and angular-shared-ui-kit establish what a shared component
must support (form-factory building blocks, a generic data table, dialogs, toasts,
confirmation prompts). This skill is about proving that contract holds visually, release
after release — a shared ButtonComponent used on 40 screens can regress silently in a
one-line SCSS change, and nothing in a unit test suite would ever notice.
Check A — No Storybook (or equivalent) for the shared component library (VRT-001)
Detection
Check whether the shared component library (the same library angular-shared-libraries
extracts form factories/data tables into, and angular-shared-ui-kit extracts
dialogs/toasts/confirmations into) has a .storybook/ config and a *.stories.ts file per
exported component. Without an isolated playground, the only way to see a component's full
variant surface (size, state, theme) is to hunt down every screen that happens to use it —
and some variants (error state on a rarely-hit form) may not be reachable in the running
app at all.
BAD — shared library ships components with no isolated playground
libs/ui-kit/
├── src/lib/button/button.component.ts
├── src/lib/dialog/dialog.component.ts
└── src/lib/data-table/data-table.component.ts
<!-- No .storybook/, no *.stories.ts anywhere. The only way to see every button variant
is to grep the app for <ui-button> usages and hope you found them all. -->
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 First seen · 250 lines · 98 tokens per session scan A d16387d0a755
angular-visual-regression-testing is a skill published in the GitHub repository AgenticPawan/FullStack-Pilot (2 stars, last pushed 2mo ago), licensed MIT. It adds 98 tokens to every session and 2,287 once invoked, about $0.0004 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
test-scenarios
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation.
azure-cosmos-db-py
Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service layer classes with CRUD operations, partition key strategies, parameterized queries, or TDD patterns for Cosmos. Triggers…
Karma Testing
Comprehensive Karma test runner skill for browser-based JavaScript unit testing with Jasmine, Mocha, or QUnit frameworks, real browser execution, coverage reporting, and CI/CD pipeline integration.
ak-test
Set up testing and debug common issues in Agent Kernel projects. This skill guides you through configuring the built-in test framework, writing agent tests, choosing test modes (score, llm, fallback), and troubleshooting common errors.
thousandeyes
ThousandEyes network intelligence integration for monitoring tests, alerts, agents, Internet Insights outages, dashboards, and BGP routes during RCA investigations.
cloudbees
CloudBees CI integration for investigating builds, deployments, pipeline stages, and test results during RCA.