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 chf3198/copilot-governance --skill repo-structure-conventionsgit clone --depth 1 https://github.com/chf3198/copilot-governanceWrote 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/chf3198/copilot-governance/repo-structure-conventions)<a href="https://agentmods.dev/skills/chf3198/copilot-governance/repo-structure-conventions"><img src="https://agentmods.dev/badge/skills/chf3198/copilot-governance/repo-structure-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/chf3198/copilot-governance/repo-structure-conventions"><img src="https://agentmods.dev/badge/skills/chf3198/copilot-governance/repo-structure-conventions.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.00032 | $0.02815 |
| Opus 5 | $0.00016 | $0.01407 |
| Sonnet 5 | $0.00006 | $0.00563 |
| Haiku 4.5 | $0.00003 | $0.00281 |
Grade A, and why
repo-structure-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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Structure Conventions
Purpose
Ensure every managed repository has a consistent, navigable, industry-standard file organization. This skill is the primary owner for structural layout, naming, and build-artifact isolation.
When to invoke
- Creating a new repository.
- Restructuring an existing repository.
- Onboarding a repo that lacks clear organization.
- After
repo-onboarding-standardsclassifies the app type.
Scope boundary
Owns (primary authority)
- Root-level file layout and ordering.
- Directory naming conventions.
- App-type-specific directory structures.
- Build artifact isolation (.gitignore, .vscodeignore, .npmignore).
- CODEOWNERS patterns by project size and structure.
Delegates (do NOT duplicate)
| Concern | Owner |
|---|---|
| Community health files (README, LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, SUPPORT) | repo-profile-governance |
| Discoverability metadata (description, topics, social preview, homepage) | repo-profile-governance |
| GitHub Actions security (SHA pinning, token permissions, OIDC) | github-actions-security-hardening |
| Secret hygiene (.env, credentials, artifact leaks) | secret-exposure-prevention |
| Documentation content quality and drift detection | docs-drift-maintenance |
| Release versioning, tags, and publish integrity | release-version-integrity |
| CI/CD workflow design and merge gates | github-review-merge-admin |
Hard constraints
- No unbounded loops or recursive retries.
- Maximum one full repository audit per invocation.
- No silent file creation; produce explicit proposals for review.
- Never move or rename files without confirming the change won't break imports, CI, or published paths.
- Prefer the smallest structural change that achieves the convention.
Modes
- audit: Detect structural gaps and deviations. Return findings ranked by severity.
- scaffold: Generate the initial directory structure for a new project given an app type.
- remediate: Propose minimal file moves/renames to bring an existing repo into compliance.
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 · 311 lines · 32 tokens per session scan A 316f77d95094
repo-structure-conventions is a skill published in the GitHub repository chf3198/copilot-governance (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 2,815 once invoked, about $0.0002 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…