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 agentmods add skills/pssah4/digital-innovation-agents/codingnpx skills add pssah4/digital-innovation-agents --skill codinggit 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/coding)<a href="https://agentmods.dev/skills/pssah4/digital-innovation-agents/coding"><img src="https://agentmods.dev/badge/skills/pssah4/digital-innovation-agents/coding.svg" alt="Measured on agentmods" 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 | $0.00075 | $0.03382 |
| Opus 5 | $0.00037 | $0.01691 |
| Sonnet 5 | $0.00015 | $0.00676 |
| Haiku 4.5 | $0.00007 | $0.00338 |
Grade A, and why
coding 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 4d 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding -- review, handoff and living documents
Two entry conditions:
- Implementation entry (typical): a FEAT / IMP / ADR / FIX is ready to be built. The full review-implement-writeback flow applies.
- Bug-capture entry: the user reports a bug outside an active
implementation run. Capture the FIX artefact without forcing an
immediate fix:
references/bug-capture.md. Trivial bugs may take the hotfix lane (fix-now, document-after, five conditions):references/hotfix-lane.md.
The actual implementation is done by the default Claude Code agent. This skill loads and reviews context, persists the plan, hands the binding protocols to the agent, and keeps the artifacts in sync.
MANDATORY Pre-Phase 0: Branch and item check
Standard ritual, full rules in
skills/project-conventions/references/team-workflow.md: identify the
active item (BACKLOG row first for anything new), verify the branch
matches <type>/<item-id-lower>-<slug> (AskUserQuestion on mismatch),
run flow.py create-issue + open-draft-pr when GitHub sync is on,
tag the phase at ritual end (--phase code), and write
.git/dia-active-skill so subsequent invocations stay silent.
MANDATORY Phase 0: Artifact triage
Before any code, doc, or spec change, determine the artifact category:
new FEATURE, IMP on an existing feature, FIX for a bug, or
ADR for an architecture decision. A DIA-Triage trailer on a
prior commit for this item answers the question; otherwise, if the
assignment cannot be derived unambiguously from the prompt, ask ONE
short question before anything else:
"Is this a new feature, an improvement on an existing feature, or a fix for a bug? If feature or IMP/FIX: which feature and which epic?"
No code or spec change without this assignment. FIX and IMP require
feature: and epic: in the frontmatter. Decision tree and
exceptions:
skills/project-conventions/references/graph-invariants.md.
MANDATORY: Backlog as single source of truth
What ships with it
13 files 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.
- references/bug-capture.md 1.5 KB
- references/debugging-protocol.md 2.4 KB
- references/deferred-stub-convention.md 1.7 KB
- references/handoff-ritual-formats.md 2.0 KB
- references/hotfix-lane.md 1.5 KB
- references/mid-course-triggers.md 5.3 KB
- references/plan-coverage-gate.md 2.1 KB
- references/reachability-by-stack.md 11 KB
- references/tdd-protocol.md 1.8 KB
- references/verification-gate-subtypes.md 3.0 KB
- templates/FIX-TEMPLATE.md 655 B
- templates/IMP-TEMPLATE.md 541 B
- templates/PLAN-TEMPLATE.md 1.2 KB
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.
- 4d ago First seen · 325 lines · 75 tokens per session scan A fe062f904ae1
coding is a skill published in the GitHub repository pssah4/digital-innovation-agents (39 stars, last pushed 23d ago), licensed MIT. It adds 75 tokens to every session and 3,382 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).
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
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-docs
Prowler documentation style guide and writing standards. Trigger: When writing documentation for Prowler features, tutorials, or guides.