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 pssah4/digital-innovation-agents --skill dia-realigngit clone --depth 1 https://github.com/pssah4/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-realign)<a href="https://agentmods.dev/skills/pssah4/digital-innovation-agents/dia-realign"><img src="https://agentmods.dev/badge/skills/pssah4/digital-innovation-agents/dia-realign/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-realign"><img src="https://agentmods.dev/badge/skills/pssah4/digital-innovation-agents/dia-realign.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 247 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 291 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Agent Snooping · line 21 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00078 | $0.05433 |
| Opus 5 | $0.00039 | $0.02717 |
| Sonnet 5 | $0.00016 | $0.01087 |
| Haiku 4.5 | $0.00008 | $0.00543 |
Grade A, and why
dia-realign 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 — 449 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DIA realign
Successor of the retired /reverse-engineering and /dia-migration
skills. You bring a repo that predates current DIA conventions in
line with them: reverse-engineer V-Model artifacts from the code,
migrate legacy DIA artifacts with the scripts under
tools/migration/, or both.
Writing style, three-layer model, frontmatter spec. See
skills/project-conventions/SKILL.md#canonical-specs; binding for
every artifact this skill produces. Status, phase, last-change, and
claim live in the backlog row, not in artifact frontmatter.
MANDATORY mode selection (first step)
Run python3 tools/migration/detect_state.py and pick the mode from
the JSON report:
| Detection result | Mode |
|---|---|
No _devprocess/ (recommendation brownfield-call-dia-realign-first) |
A: full reverse walk |
Legacy DIA signals: old IDs, HANDOFFS.md, v1/v2 layout (recommendation run-full-migration) |
B: script pass, then gap walk |
Current artifacts (recommendation v2-clean-no-migration-needed) |
C: gap walk and deprecations only |
empty-repo |
Not this skill. Greenfield starts at /business-analysis. |
Confirm the detected mode with the user before writing anything. Mixed states resolve toward B: the script pass is idempotent.
MANDATORY Pre-Phase 0: branch check
Standard ritual, full rules in
skills/project-conventions/references/team-workflow.md: Mode A runs
on feature/realign-<repo-name> (multi-item exception: one branch
bootstraps the whole backlog, per-item branches start AFTER merge;
full exception rules:
skills/project-conventions/references/branch-protection.md);
Modes B and C run on chore/dia-realign-<YYYY-MM-DD>. Refuse on
main / master / dev (AskUserQuestion to create and switch), no
per-item issues or phase tags during the walk, write
.git/dia-active-skill so subsequent invocations stay silent.
MANDATORY Phase 0: artifact triage
Every artifact this skill creates lands in one of four categories
before writing: FEATURE (observed capability), ADR (decision
inferred from code or docs), IMP (improvement candidate), FIX
(bug or drift surfaced by the scan). Frontmatter feature: and
epic: are mandatory for FIX and IMP. A DIA-Triage trailer on a
prior commit for an item answers the category question for that item.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 449 lines · 78 tokens per session scan A 85323a3fca3a
dia-realign is a skill published in the GitHub repository pssah4/digital-innovation-agents (39 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 5,433 once invoked, about $0.0004 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.