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 ashermahonin/agentic-skills --skill project-structure-governancegit clone --depth 1 https://github.com/ashermahonin/agentic-skillsWrote 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/ashermahonin/agentic-skills/project-structure-governance)<a href="https://agentmods.dev/skills/ashermahonin/agentic-skills/project-structure-governance"><img src="https://agentmods.dev/badge/skills/ashermahonin/agentic-skills/project-structure-governance/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/ashermahonin/agentic-skills/project-structure-governance"><img src="https://agentmods.dev/badge/skills/ashermahonin/agentic-skills/project-structure-governance.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.00072 | $0.00952 |
| Opus 5 | $0.00036 | $0.00476 |
| Sonnet 5 | $0.00014 | $0.00190 |
| Haiku 4.5 | $0.00007 | $0.00095 |
Grade A, and why
project-structure-governance 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 10d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Structure Governance
Purpose
Keep the repository understandable after the agent leaves. Treat structure, temporary artifacts, test scripts, and documentation entrypoints as part of the deliverable, not as cleanup someone else will do later.
Repository state
- Read
references/project-activity-contract.md. - Identify the project type, existing conventions, and current documentation entrypoint (
README.md,docs/README.md,RUNBOOK.md,AGENTS.md,CLAUDE.md, or equivalent). - Inspect the repo root and common scratch locations for clutter: one-off scripts, generated outputs, screenshots, temp logs, duplicate instructions, abandoned migration helpers, and stale test harnesses.
- Confirm where temporary/test artifacts should live for this repo. Prefer an existing convention; otherwise use a dedicated ignored workspace such as
.agent-work/,.tmp/agent/, ortools/agent/depending on project norms. - Record any required cleanup, consolidation, or documentation-entrypoint work before implementation expands the file surface.
Structure rules
- Structure contract. Define or verify the top-level repo map: source, tests, tools, docs, scripts, infra, assets, fixtures, generated artifacts, and agent-only workspace.
- Artifact routing. Route every new file before creating it: production source, test fixture, reusable tool, temporary experiment, generated output, documentation, or project memory.
- Temporary isolation. Put throwaway scripts, debug probes, generated logs, screenshots, benchmark scratch, and exploratory outputs in the dedicated agent/test workspace. Do not place them in repo root.
- Reusable promotion. Promote a temporary script only if it has a stable name, documented purpose, safe flags, validation command, owner, and a permanent home such as
tools/,scripts/,tests/fixtures/, ordocs/examples/. - Documentation entrypoint. Maintain one canonical entrypoint that links outward: README for project overview,
docs/README.mdfor deep docs when needed, and one runbook/index for operation. Avoid multiple competing “START_HERE”, “HOW_TO”, “FINAL”, “NEW_README”, or duplicate setup files. - Runbook hygiene. If operational commands, install steps, local dev setup, release, rollback, or incident response changed, update the canonical runbook/index instead of adding a standalone note.
- Root cleanliness check. Before handoff, verify the repo root contains only intentional files. Move, delete, or document anything temporary according to the contract.
- Graph update. Hand documentation changes to
documentation-graph-curatorso Obsidian memory points to the canonical entrypoint and does not preserve obsolete instructions as current truth.
What ships with it
2 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.
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.
- 10d ago First seen · 62 lines · 72 tokens per session scan A b28db9a72269
project-structure-governance is a skill published in the GitHub repository ashermahonin/agentic-skills (10 stars, last pushed 16d ago), licensed MIT. It adds 72 tokens to every session and 952 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…