architecture

architecture is a skill for Claude Code from pssah4/digital-innovation-agents. It costs 75 tokens per session (2,204 once invoked), scanned A, original, MIT.

A planning guide for recording software architecture decisions, project constraints, system maps, and references for coding work.

In plain words
What is it for?
Use it to propose or record architecture decisions, describe technical constraints, map system components, route decisions, and prepare context for implementation.
Why use it?
It gives a project a traceable way to explain design choices and keep architecture-related documents connected to the active work item.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: names the AskUserQuestion tool; mentions Claude Code; mentions AGENTS.md.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 tools/github-integration/flow.py tag-phase --item <ID> --phase arch.

Part of the digital-innovation-agents plugin — 13 skills, 1 hook shipped together

Good fit Use it to propose or record architecture decisions, describe technical constraints, map system components, route decisions, and prepare context for implementation.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/pssah4/digital-innovation-agents
agentmods
npx agentmods add skills/pssah4/digital-innovation-agents/architecture

Made for: Claude Code.

Or install digital-innovation-agents, the plugin that ships this one along with the rest of its 13 skills, 1 hook.

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 architecture

README.md
[![agentmods](https://agentmods.dev/badge/skills/pssah4/digital-innovation-agents/architecture/github.svg)](https://agentmods.dev/skills/pssah4/digital-innovation-agents/architecture)
Your own site
<a href="https://agentmods.dev/skills/pssah4/digital-innovation-agents/architecture"><img src="https://agentmods.dev/badge/skills/pssah4/digital-innovation-agents/architecture/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.

agentmods 80×15 button for architecture

Your own site · 80×15
<a href="https://agentmods.dev/skills/pssah4/digital-innovation-agents/architecture"><img src="https://agentmods.dev/badge/skills/pssah4/digital-innovation-agents/architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,204 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, 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 37
    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.
  • medium Agent Snooping · line 57
    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.
How audits are shown
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.00075 $0.02204
Opus 5 $0.00037 $0.01102
Sonnet 5 $0.00015 $0.00441
Haiku 4.5 $0.00007 $0.00220

Measured 11d ago against content hash 653086779bec, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

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

skills/architecture/SKILL.md · 234 lines

How it starts

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

Architect

You turn requirements into architecture proposals: ADRs, the arc42 constraints doc, and a compact plan-context.md ref index for /coding. In the lean profile this skill is the core of the workflow: it owns the rules in AGENTS.md, SYSTEM-MAP.md, and the post-hoc decision records behind decisions/README.md.

Input: Epics, Features, ASRs, NFRs from Requirements Engineering (full profile), or the running codebase (lean, post-hoc). Output: ADRs, arc42 constraints, plan-context.md, navigation artifacts.

Hard rules

  1. Branch and item check first. Identify the active item, verify feature/<item-id-lower>-<slug>, then run create-issue and open-draft-pr via tools/github-integration/flow.py. Full procedure: skills/project-conventions/references/team-workflow.md.
  2. Triage every change: New FEATURE, IMP, FIX, or ADR. Ask once if ambiguous. FIX and IMP require feature: and epic: in frontmatter. Decision tree: skills/project-conventions/references/graph-invariants.md.
  3. Backlog row before artifact body. Status, phase, claim, last-change, refs live in the row, not in frontmatter. See skills/project-conventions/SKILL.md#canonical-specs (Backlog vocabulary, Frontmatter spec).
  4. Wayfinder is the only place for current code paths. New concept from an ADR adds a row to src/ARCHITECTURE.map. New module gets a README.md at the module root. Templates in templates/.
  5. ADR abstraction. Core sections (Context, Decision Drivers, Considered Options, Decision, Consequences) carry no code paths, file names, line numbers, or signatures. Code-level hints belong in the optional ## Implementation Notes appendix.
  6. ADR consolidation duty. Before a new ADR, check if an existing one can be merged, amended, or extended. Report consolidation moves in the Handoff Ritual.
  7. Rule-set owner. _devprocess/rules/technical.md (max 150), design.md (max 100 if UI), domain.md (max 100). Hard cap 500 lines total. Templates in templates/.
  8. Dependencies via depends-on: [ID, ...] in frontmatter. Graph stays acyclic. Details: graph-invariants.md.
  9. Epic hypothesis statements and How-Might-We headings as full prose, no FOR / WHO / THE / IS A placeholders left over.
  10. Writing style. See skills/project-conventions/SKILL.md#canonical-specs (Writing style). Scan the artifact before save.

Read the full file on GitHub · 234 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. 11d ago First seen · 234 lines · 75 tokens per session scan A 653086779bec

Subscribe to this mod's changes

architecture is a skill published in the GitHub repository pssah4/digital-innovation-agents (39 stars, last pushed 29d ago), licensed MIT. It adds 75 tokens to every session and 2,204 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.

Related

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-cloud/prowler · 64 tokens

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-cloud/prowler · 84 tokens

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-cloud/prowler · 62 tokens

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-cloud/prowler · 47 tokens

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

prowler-docs

Prowler documentation style guide and writing standards. Trigger: When writing documentation for Prowler features, tutorials, or guides.

prowler-cloud/prowler · 31 tokens