bootstrap-diagnostics

bootstrap-diagnostics is a skill for OpenCode from cruzs85/opencode-multiagente-local-37-iterations. It costs 47 tokens per session (800 once invoked), scanned A, original, MIT.

A troubleshooting guide for Angular startup failures that leave a blank page even when the build succeeds. It focuses on problems that appear in browser tests or continuous integration systems.

In plain words
What is it for?
Use it to investigate a blank Angular page, verify the root component and its import in main.ts, check for duplicate selectors, and run a minimal startup test.
Why use it?
It helps find silent startup mistakes when end-to-end tests report that expected page elements cannot be found. It checks common causes such as duplicate root components, wrong imports, and outdated style settings.

Skill for OpenCode

Written for OpenCode: installed under .opencode/.

Good fit Use it to investigate a blank Angular page, verify the root component and its import in main.ts, check for duplicate selectors, and run a minimal startup test.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cruzs85/opencode-multiagente-local-37-iterations/bootstrap-diagnostics
Install

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.

Any agent
npx skills add cruzs85/opencode-multiagente-local-37-iterations --skill bootstrap-diagnostics
Clone the repo
git clone --depth 1 https://github.com/cruzs85/opencode-multiagente-local-37-iterations

Made for: OpenCode.

Wrote 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.

agentmods badge for bootstrap-diagnostics

README.md
[![agentmods](https://agentmods.dev/badge/skills/cruzs85/opencode-multiagente-local-37-iterations/bootstrap-diagnostics.svg)](https://agentmods.dev/skills/cruzs85/opencode-multiagente-local-37-iterations/bootstrap-diagnostics)
Your own site
<a href="https://agentmods.dev/skills/cruzs85/opencode-multiagente-local-37-iterations/bootstrap-diagnostics"><img src="https://agentmods.dev/badge/skills/cruzs85/opencode-multiagente-local-37-iterations/bootstrap-diagnostics.svg" alt="Measured on agentmods" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 800 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.00800
Opus 5 $0.00023 $0.00400
Sonnet 5 $0.00009 $0.00160
Haiku 4.5 $0.00005 $0.00080

Measured 8d ago against content hash f641be7227c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

bootstrap-diagnostics scanned grade A with 1 finding 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 8d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

5. Test: `curl -s http://localhost:4200 | grep BOOT_OK`
configuraciones/configuracion-19(handoff-json)/.opencode/skills/bootstrap-diagnostics/SKILL.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: bootstrap-diagnostics

Propósito

Detectar errores silenciosos de arranque de Angular en entornos headless (Playwright, CI) donde el build es exitoso pero la página aparece en blanco.

Cuándo usarla

  • Build exitoso pero página en blanco
  • Tests E2E fallan consistentemente con "element not found"
  • No hay errores visibles en consola del servidor

Procedimiento

Paso 1: Verificar selectores duplicados (causa #1)

Ejecutar:

grep -rn "selector:" src/app/

Si hay 2+ componentes definiendo app-root, esa es la causa. Ejemplo de conflicto:

  • src/app/app.component.ts: selector: 'app-root'
  • src/app/app.ts: selector: 'app-root' (legacy de ng new)

Solución: Eliminar el archivo legacy y verificar que main.ts importe el correcto.

Paso 2: Verificar imports de main.ts

Ejecutar:

cat src/main.ts

Confirmar que importa AppComponent desde ./app/app.component, NO App desde ./app/app.

Paso 3: Verificar styleUrls (plural)

Ejecutar:

grep -rn "styleUrls" src/app/

Si hay matches, Angular 21+ con Vite build puede fallar silenciosamente.

Paso 4: Prueba de bootstrap mínimo

  1. Reemplazar temporalmente el template de AppComponent con <h1>BOOT_OK</h1>
  2. Eliminar todos los imports de subcomponentes del template
  3. Build: npm run build
  4. Servir: npx http-server ./dist/dino-runner/browser -p 4200 -c-1 &
  5. Test: curl -s http://localhost:4200 | grep BOOT_OK
    • Si aparece "BOOT_OK" → el error está en subcomponentes o servicios
    • Si NO aparece → el error es estructural (Angular no arranca)

Paso 5: Verificar errores en Playwright

En tests E2E, capturar todos los errores:

const errors: string[] = [];
page.on('pageerror', err => errors.push(err.message));
page.on('console', msg => {
  if (msg.type() === 'error') errors.push(msg.text());
});
await page.goto('http://localhost:4200');
await page.waitForTimeout(2000);
console.log('Captured errors:', errors);

Paso 6: Verificar que Angular está presente

curl -s http://localhost:4200 | grep -o "ng-version=[^ ]*" | head -1

Si no aparece ng-version, Angular no se bootstraped.

Read the full file on GitHub · 80 lines

Changes

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.

  1. 8d ago First seen · 80 lines · 47 tokens per session scan A f641be7227c6

Subscribe to this mod's changes

bootstrap-diagnostics is a skill published in the GitHub repository cruzs85/opencode-multiagente-local-37-iterations (5 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 800 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

inspecting-hermes-desktop-dom

Read the live Hermes desktop DOM/CSS over CDP.

NousResearch/hermes-agent · 20 tokens

a11y-debugging

Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.

ChromeDevTools/chrome-devtools-mcp · 50 tokens

copilotkit-debug

Use when diagnosing CopilotKit issues -- runtime connectivity failures, agent not responding, streaming errors, tool execution problems, transcription failures, version mismatches, and AG-UI event tracing.

CopilotKit/CopilotKit · 42 tokens

devtools

Drop-in inspector panel for any json-render app. Use when the user wants to debug a generative UI, inspect the spec tree, edit state at runtime, see dispatched actions, follow stream patches live, browse a catalog, or pick DOM elements to find their spec keys. Triggers include "add devtools", "debug json-render"…

vercel-labs/json-render · 108 tokens

migrate-oxlint

Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.

oxc-project/oxc · 44 tokens

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens