Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add pssah4/digital-innovation-agents/plugin install digital-innovation-agentsWrote 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/pssah4/digital-innovation-agents/dia-bootstrap)<a href="https://agentmods.dev/skills/pssah4/digital-innovation-agents/dia-bootstrap"><img src="https://agentmods.dev/badge/skills/pssah4/digital-innovation-agents/dia-bootstrap/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/pssah4/digital-innovation-agents/dia-bootstrap"><img src="https://agentmods.dev/badge/skills/pssah4/digital-innovation-agents/dia-bootstrap.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.00063 | $0.01180 |
| Opus 5 | $0.00032 | $0.00590 |
| Sonnet 5 | $0.00013 | $0.00236 |
| Haiku 4.5 | $0.00006 | $0.00118 |
Grade A, and why
dia-bootstrap 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 11d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DIA Bootstrap
You have access to a structured V-Model workflow for AI-augmented innovation and development, from business concept through requirements, architecture, implementation, testing, and security audit.
Helper script paths (binding for every phase skill)
Plugin helper scripts (tools/github-integration/flow.py,
tools/dia-setup/anchor.py, tools/migration/*,
tools/consistency-check.py, scripts/*) live in the plugin bundle,
NOT in the user project. Resolve every tools/... and scripts/...
path in skill text against the plugin root, in this priority:
$DIA_PLUGIN_ROOT(preferred; printed by the SessionStart hook)$CLAUDE_PLUGIN_ROOT(Claude Code)$CURSOR_PLUGIN_ROOT(Cursor)- Working directory (last resort, plugin checkout only)
Example: python3 tools/github-integration/flow.py ... expands to
python3 "$DIA_PLUGIN_ROOT/tools/github-integration/flow.py" ....
If no variable resolves, surface a clear error and link the
installation tutorial.
Do not guess.
Activation
No .dia/config.toml yet? Run /dia-setup first. It asks for the
mode (off: hooks silent, skills advisory only; git-only: local
commits, tags, merge scripts; github-sync: backlog mirrored to
GitHub issues via flow.py) and the profile (below), then writes the
config and the anchor blocks. Re-run /dia-setup any time.
Profiles
profile in .dia/config.toml controls how much of the V-Model is
binding. A missing field means full.
full: every phase skill is binding as written.lean: only durable decisions and stable navigation are binding: rules consolidated in AGENTS.md (CLAUDE.md stays a pointer),_devprocess/SYSTEM-MAP.mdfor code navigation, post-hoc ADRs (kind: post-hoc) behinddecisions/README.mdas a router table, and backlog state (GitHub Issues ingithub-sync, a thin BACKLOG.md ingit-only). All other phase skills stay available as advisory tools; no gate blocks, no BA/FEATURE artifacts are required, handoffs reduce to phase-end commits with DIA trailers. Guiding rule in lean: never document what code, tests, git, PRs, or issues already carry.
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.
- 11d ago First seen · 112 lines · 63 tokens per session scan A c39108c7216c
dia-bootstrap is a skill published in the GitHub repository pssah4/digital-innovation-agents (39 stars, last pushed 29d ago), licensed MIT. It adds 63 tokens to every session and 1,180 once invoked, about $0.0003 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-30.
Other skills, from other repositories
prowler-ui
Prowler UI-specific patterns. For generic patterns, see: typescript, react-19, nextjs-16, tailwind-4. Trigger: When working inside ui/ on Prowler-specific conventions (shadcn, folder placement, actions/adapters, shared types/hooks/lib).
prowler-pr
Creates Pull Requests for Prowler following the project template and conventions. Trigger: When working on pull request requirements or creation (PR template sections, PR title Conventional Commits check, changelog gate/no-changelog label), or when inspecting PR-related GitHub workflows like conventional-commit.yml…
prowler-test-api
Testing patterns for Prowler API: JSON:API, Celery tasks, RLS isolation, RBAC. Trigger: When writing tests for api/ (JSON:API requests/assertions, cross-tenant isolation, RBAC, Celery tasks, viewsets/serializers).
tailwind-4
Tailwind CSS 4 patterns and best practices. Trigger: When styling with Tailwind (className, variants, cn()), especially when dynamic styling or CSS variables are involved (no var() in className).
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
prowler-docs
Prowler documentation style guide and writing standards. Trigger: When writing documentation for Prowler features, tutorials, or guides.