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 agentmods add instructions/calsora/power-platform-github-copilot-kit/clean-codegit clone --depth 1 https://github.com/calsora/power-platform-github-copilot-kitWhat 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 | $0.01156 | $0.01156 |
| Opus 5 | $0.00578 | $0.00578 |
| Sonnet 5 | $0.00231 | $0.00231 |
| Haiku 4.5 | $0.00116 | $0.00116 |
Grade A, and why
power-platform-github-copilot-kit clean-code.instructions.md 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 yesterday.
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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Code Instructions
This guidance summarizes essential clean code principles for HTML, JavaScript, TypeScript, and C# projects. Use it as a shared code quality baseline across projects.
Why clean code matters
- Clean code is easy to understand, review, and maintain.
- It reduces defects and makes changes safer.
- It keeps teams aligned around consistent naming, structure, and intent.
General rules
- Follow standard conventions for the language and framework.
- Keep it simple. Simpler solutions are easier to read and change.
- Leave code cleaner than you found it.
- Find and fix root causes, not just symptoms.
Design rules
- Keep configurable data at high levels.
- Prefer polymorphism or strategy patterns over long
if/elseorswitchchains. - Keep concurrency and async control logic separate from business logic.
- Avoid over-configurability and unnecessary indirection.
- Use dependency injection where it improves testability and decoupling.
- Follow the Law of Demeter: use only direct dependencies.
Understandability tips
- Be consistent in style, naming, and structure.
- Use explanatory variables and clear expressions.
- Encapsulate boundary conditions and edge-case logic.
- Prefer domain-specific value objects over raw primitives.
- Avoid hidden dependencies between methods or modules.
- Avoid negative conditionals when a positive form is clearer.
Names rules
- Choose descriptive, unambiguous names.
- Make meaningful distinctions between similar concepts.
- Use pronounceable names.
- Use searchable names that are easy to find in the codebase.
- Replace magic numbers with named constants.
- Avoid encoding type or prefix information in names.
Functions and methods
- Keep functions small.
- Do one thing per function.
- Use descriptive names.
- Prefer fewer arguments.
- Avoid side effects whenever possible.
- Don’t use flag arguments; split behavior into separate functions.
Comments
- Prefer self-explanatory code to comments.
- Don’t add redundant comments.
- Avoid noisy comments that state the obvious.
- Don’t use closing-brace comments.
- Don’t leave commented-out code in the repository.
- Use comments to explain intent, clarify decisions, or warn about consequences.
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.
- yesterday First seen · 146 lines · 1,156 tokens per session scan A 03538b74279b
power-platform-github-copilot-kit clean-code.instructions.md is an instructions file published in the GitHub repository calsora/power-platform-github-copilot-kit (6 stars, last pushed 2mo ago), licensed MIT. It adds 1,156 tokens to every session, about $0.0058 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.