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 project-conventionsgit 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/project-conventions)<a href="https://agentmods.dev/skills/pssah4/digital-innovation-agents/project-conventions"><img src="https://agentmods.dev/badge/skills/pssah4/digital-innovation-agents/project-conventions/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/project-conventions"><img src="https://agentmods.dev/badge/skills/pssah4/digital-innovation-agents/project-conventions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Agent Snooping · line 129 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.00062 | $0.01412 |
| Opus 5 | $0.00031 | $0.00706 |
| Sonnet 5 | $0.00012 | $0.00282 |
| Haiku 4.5 | $0.00006 | $0.00141 |
Grade A, and why
project-conventions 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project structure and conventions
This skill defines the binding standards for directory structures, file
names, and ways of working. All other skills (BA, RE, Architecture,
Coding, Testing, Security Audit) follow these conventions. Details live
in references/; load a reference file only when the task touches its
area.
Codebase-awareness (core principle)
All skills operate in the context of the existing codebase, never in a
vacuum. Read references/codebase-awareness.md for the complete rules.
Summary: before any work, read existing code, recognize patterns,
understand dependencies, check reference implementations. The project's
CLAUDE.md takes PRECEDENCE over generic skill instructions.
Canonical Specs (single home; other skills link here)
Index. Full detail: references/canonical-specs.md. Phase skills and
templates never restate these specs; they link here.
- Reader budget. Every artifact scannable in under two minutes,
enforced as per-artifact line caps in the single source
references/artifact-caps.json(read at runtime by/consistency-check; never mirror the values). Exceeding a cap needs a one-line## Reasoned exceptionblock at the top of the file, added only with justification, never routinely. ARCHITECTURE-MAP, MODULE-README, JSDOC-HEADER and RULES-* carry their caps in their template comments. - Frontmatter spec. Identity and relations only;
status,phase,author,claimare forbidden (N-15). Empty refs are omitted, never stubbed. Full key list in the reference. - Backlog vocabulary. Binding column order, GitHub-aligned status
values, phase tags
<id>/<phase>-done, DIA commit trailers (DIA-Phase,DIA-Handoff,DIA-Triage), ID schema, Claim and Refs column formats. Full vocabulary in the reference. - Writing style. Zero em/en dashes, no AI vocabulary, active
voice, sentence case in headings. Blacklist and pre-save scan:
references/writing-style.md(single home, also used by/humanizer). - Activation Path format. Fixed
## Activation Pathsection in every FEATURE spec, parsed by N-18. Exact format in the reference. - Priority / Effort legend. P0-P3 and XS-XL definitions in the reference. XL at FEAT scope means: split first.
- Three-layer model. Wayfinder / rule sets / backlog / detail
artifacts with binding boundaries, the ADR abstraction rule (A-1)
and the ADR/FEATURE/PLAN separation:
references/three-layer-model.md. - Section policy. Sections are emitted only when they carry
decision content; optional sections live in template comments, not
as
TBDplaceholders.
What ships with it
12 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/artifact-caps.json 2.6 KB
- references/backlog-sot.md 2.1 KB
- references/branch-protection.md 8.7 KB
- references/canonical-specs.md 12 KB
- references/codebase-awareness.md 1.9 KB
- references/directory-structure.md 5.5 KB
- references/graph-invariants.md 31 KB
- references/naming-conventions.md 4.9 KB
- references/team-workflow.md 19 KB
- references/three-layer-model.md 4.1 KB
- references/user-interaction-protocol.md 1.9 KB
- references/writing-style.md 3.5 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.
- 11d ago First seen · 135 lines · 62 tokens per session scan A 27f46aed1bee
project-conventions is a skill published in the GitHub repository pssah4/digital-innovation-agents (39 stars, last pushed 29d ago), licensed MIT. It adds 62 tokens to every session and 1,412 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.