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.
git clone --depth 1 https://github.com/sdcorejs/sdcorejs-agentWrote 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/commands/sdcorejs/sdcorejs-agent/sdcorejs-angular-smoke-tests.vi)<a href="https://agentmods.dev/commands/sdcorejs/sdcorejs-agent/sdcorejs-angular-smoke-tests.vi"><img src="https://agentmods.dev/badge/commands/sdcorejs/sdcorejs-agent/sdcorejs-angular-smoke-tests.vi/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/commands/sdcorejs/sdcorejs-agent/sdcorejs-angular-smoke-tests.vi"><img src="https://agentmods.dev/badge/commands/sdcorejs/sdcorejs-agent/sdcorejs-angular-smoke-tests.vi.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.00000 | $0.00514 |
| Opus 5 | $0.00000 | $0.00257 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
sdcorejs-angular-smoke-tests.vi 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDCoreJS Angular Portal Localized-Intent Smoke Test Pack
This source file stays English-only. When using these cases at runtime, translate the prompt text into the target language instead of hardcoding localized prose in this repository.
Use these cases in VS Code Chat with SDCoreJS mode to validate localized intent handling for Angular portal work.
Prompt 1
Create product CRUD with fields code, name, price.
Prompt 2
Create a customer screen. No suitable module exists yet, so create one first.
Prompt 3
Create order CRUD in the sales module. Fields will be refined later.
Prompt 4
Create supplier detail with 6 fields: code, name, phone, email, status, note. Use standard CRUD.
Prompt 5
Create a purchase request screen in the procurement module. Need create, update, detail, submit, approve, and reject. The list page needs bulk submit and bulk approve. The detail page has sections, item child table, and attachment review.
Prompt 6
Initialize a new portal starter from the Angular init refs and templates in sdcorejs-agent/_refs/angular. Keep the starter shell plus mandatory src/libs/sample scaffold. Do not keep unnecessary tsconfig settings.
Prompt 7
Initialize a portal starter in a brand-new workspace. Package versions must match the package guidance in sdcorejs-agent/_refs/angular/core-version.md and the Angular init refs. Do not infer or upgrade versions from any external sample repository. Do not use file:*.tgz dependencies for @sdcorejs/angular. Support starter home page under src/app/pages/home and wire LayoutConfiguration.homeUrl. Generate src/libs/sample with employee and product seeded.
What To Validate
- Missing module asks clarification first.
- Missing module fallback creates the module first.
- Vague fields start with a minimal skeleton.
- Simple forms default to side-drawer.
- Complex workflows default to full page plus detail/list workflow actions.
- Portal init tsconfig should not keep compilerOptions.baseUrl unless there is a clear import-resolution reason.
- Portal init includes src/libs/sample with seeded employee and product entities.
- Portal init in a new workspace keeps package versions aligned to the local baseline guidance.
- Portal init keeps @sdcorejs/angular as a normal npm version string, not file:*.tgz.
- Portal init supports a customizable home page through src/app/pages/home and LayoutConfiguration.homeUrl.
- Portal init creates src/libs/sample/modules/employee and src/libs/sample/modules/product.
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 · 57 lines · 0 tokens per session scan A d072562273e8
sdcorejs-angular-smoke-tests.vi is a command published in the GitHub repository sdcorejs/sdcorejs-agent (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 514 tokens. 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-09-08.
Other commands, from other repositories
test-bar
Generate a floating QA test overlay for the current branch's UI changes. Use when user says /test-bar, needs visual QA scenarios, or wants to test conditional rendering paths.
wp-responsive-check
Responsive validation — screenshots at 5 viewports, checks for layout issues.
stark-qa
Use this command to require proof before calling a UI "good.".
build-from-figma
You are the master orchestrator for converting a Figma design into a fully working, tested React application. You receive a Figma URL and guide the entire process through 9 phases, using specialized skills and agents.
test
Generate Vitest tests for Vue components or functions.
component-scaffold
You are a React component architecture expert specializing in scaffolding production-ready, accessible, and performant components. Generate complete component implementations with TypeScript, tests, styles, and documentation following modern best practices.