Borrowing it
Nothing to install: this file belongs to vepo/issues. 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/vepo/issues/main/.claude/skills/review-code-structure/SKILL.mdgit clone --depth 1 https://github.com/vepo/issuesWrote 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/vepo/issues/review-code-structure)<a href="https://agentmods.dev/skills/vepo/issues/review-code-structure"><img src="https://agentmods.dev/badge/skills/vepo/issues/review-code-structure/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/vepo/issues/review-code-structure"><img src="https://agentmods.dev/badge/skills/vepo/issues/review-code-structure.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00035 | $0.00527 |
| Opus 5.5 | $0.00014 | $0.00211 |
| Sonnet 5.5 | $0.00007 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
review-code-structure 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 1mo 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Java architect reviewing the Issues codebase. Produce a read-only structural audit — do not change code unless the user explicitly asks to fix findings afterward.
Prerequisites: Read ARCHITECTURE.md and docs/domain-specification.md before auditing.
Scope
Default: full repository (src/main/java/dev/vepo/issues/, src/main/webui/, tests).
If the user names a package or path, restrict scope but still check cross-package imports.
Output
Write one report:
reports/code-structure-review-{sequential}-{dd-MM-yyyy-HH-mm-ss}.md
Severity: critical | major | minor | suggestion.
Do not ask for confirmation before starting. Do not apply refactors in this command.
Phase 1 — Inventory
- List feature packages from ARCHITECTURE.md §5.
- Build type inventory: endpoints, repositories, services, entities, Request/Response records.
Phase 2 — Layer compliance
Read .cursor/rules/issues-layered-architecture.mdc.
| Check | Pass criteria |
|---|---|
| Endpoint → Repository bypass | Endpoints with multi-entity logic use *Service |
| Service → EntityManager | Services use repositories, not EM directly |
| Repository purity | No business rules or HTTP in repositories |
Phase 3 — HTTP contract
Read .cursor/rules/issues-http-contract.mdc.
- All
*Request/*Responseare records ArchitectureTestwould pass
Phase 4 — Bounded contexts
Read .cursor/rules/issues-bounded-contexts.mdc.
- Package dependency direction matches domain spec
- No unrelated cross-package repository access
Phase 5 — Duplication
- Repeated ticket/workflow validation logic
- Duplicate Angular HTTP calls
- Similar Response mapping patterns
Phase 6 — Frontend structure
- Services centralize API calls
- Components stay presentation-focused
Report template
# Code structure review — Issues
## Summary
(2–3 sentences)
## Findings
### Critical
- ...
### Major
- ...
### Minor / suggestions
- ...
## Recommended next steps
1. ...
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.
- 1mo ago First seen · 93 lines · 35 tokens per session scan A 30e02af813cc
review-code-structure is a skill published in the GitHub repository vepo/issues (8 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 527 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
agent-dependencies
Perform one conservative dependency or toolchain upgrade in the Elements monorepo and open a validated pull request. Use for nightly or unattended dependency maintenance, outdated package checks, first-party actions/ GitHub Actions updates, and pinned mise tool updates. Use the github-dependabot skill instead when the…
agent-debug-ci
Investigate failed scheduled or nightly GitHub Actions runs on the default branch, determine whether the failure is reproducible and repository-owned, implement the smallest evidence-backed fix, validate it, and open a pull request. Use when a failed nightly CI event starts an agent, or when the standard CI or…
audit-ci
Run and analyze Elements cold CI performance profiles and propose evidence-backed build, test, lint, and dependency-graph improvements. Use whenever asked to profile or benchmark pnpm run ci, rerun ci:profile, create a CI performance audit, compare CI timings, find bottlenecks or the completion path, investigate a CI…
authoring-projects
Author a new standalone NVIDIA Elements workspace project containing a Lit component, including package files, the five test types, Wireit tasks, workspace and CI registration, metadata generation, documentation-site integration, dependency-lint configuration, and generated lock/notice files. Use when creating or…
logic-component-shape
Decision tree for single component versus container/presenter, which componentStructure to generate, and which componentType to declare. Invoked by logic-placement and logic-review, not directly.