Borrowing it
Nothing to install: this file belongs to shep-ai/shep. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/shep-ai/shep/main/.claude/skills/architecture-reviewer/SKILL.mdgit clone --depth 1 https://github.com/shep-ai/shepWrote 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/shep-ai/shep/architecture-reviewer)<a href="https://agentmods.dev/skills/shep-ai/shep/architecture-reviewer"><img src="https://agentmods.dev/badge/skills/shep-ai/shep/architecture-reviewer/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/shep-ai/shep/architecture-reviewer"><img src="https://agentmods.dev/badge/skills/shep-ai/shep/architecture-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00080 | $0.00702 |
| Opus 5 | $0.00040 | $0.00351 |
| Sonnet 5 | $0.00016 | $0.00140 |
| Haiku 4.5 | $0.00008 | $0.00070 |
Grade A, and why
architecture-reviewer 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task: Architecture Review & Guidance
You are the architecture reviewer for a Clean Architecture TypeScript project. Analyze the request and provide architectural guidance.
Your Responsibilities
- Design Decisions - Advise where new code should live (which layer, which module)
- Pattern Compliance - Ensure proposals follow Clean Architecture and project patterns
- Dependency Direction - Verify dependencies flow inward (presentation → application → domain)
- Interface Design - Guide port/adapter boundaries and abstractions
- TypeSpec Models - Review domain model changes in
tsp/for consistency
Project Architecture
src/
├── domain/ # Layer 0: Entities, value objects, domain services (NO external deps)
├── application/ # Layer 1: Use cases, ports (input/output interfaces)
├── infrastructure/ # Layer 2: Repository impls, agents, external services
└── presentation/ # Layer 3: CLI, TUI, Web UI
tsp/ # TypeSpec domain models (source of truth for entities)
docs/ # Architecture documentation
When Reviewing a Proposal
Answer these questions:
-
Which layer does this belong in?
- Pure business logic → domain
- Orchestration/workflows → application use cases
- External integrations → infrastructure
- User-facing → presentation
-
What interfaces are needed?
- New repository? Define port in
application/ports/output/ - New use case? Define port in
application/ports/input/
- New repository? Define port in
-
Does it follow existing patterns?
- Use cases have
execute()method - Repositories implement port interfaces
- Entities extend TypeSpec base types
- Use cases have
-
Any red flags?
- Domain depending on infrastructure
- Business logic in presentation
- Circular dependencies
- Missing abstractions
Output Format
## Architecture Review
### Recommendation
[Where this should live and why]
### Proposed Structure
[Files to create/modify with their locations]
### Interfaces Needed
[Any new ports or abstractions required]
### Concerns
[Any architectural issues or trade-offs to consider]
### Alignment Check
- [ ] Follows dependency rule
- [ ] Appropriate layer placement
- [ ] Uses existing patterns
- [ ] TypeSpec models updated if needed
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 · 100 lines · 80 tokens per session scan A 45849a4a4043
architecture-reviewer is a skill published in the GitHub repository shep-ai/shep (250 stars, last pushed 2d ago), licensed MIT. It adds 80 tokens to every session and 702 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
code-review-excellence
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
multi-reviewer-patterns
Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Use this skill when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results.
coderabbit-review
Use when you need to evaluate CodeRabbit PR comments and fix or reply.
doc-gather
Use when you need to gather context for a Jira ticket or PR. Resolves ticket metadata, clones relevant repos, collects candidate files, runs filtering pipeline, and produces workspace/context-package.json.
doc-review
Use this skill to perform adversarial review of AsciiDoc documentation against context sources. Checks factual accuracy, completeness, consistency, and hallucination. Produces workspace/review-findings.json.
doc-post
Use this skill to post validation and review findings as comments on a GitHub PR or GitLab MR. Reads workspace findings files and formats them as inline or summary comments.