Borrowing it
Nothing to install: this file belongs to lilhammerfun/clumsies. 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/lilhammerfun/clumsies/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/lilhammerfun/clumsiesWrote 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/instructions/lilhammerfun/clumsies/copilot-instructions)<a href="https://agentmods.dev/instructions/lilhammerfun/clumsies/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/lilhammerfun/clumsies/copilot-instructions.svg" alt="Measured on agentmods" 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.00513 | $0.00513 |
| Opus 5 | $0.00257 | $0.00257 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
clumsies copilot-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 today.
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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Instructions
Development workflow (worktrees + kanban) is documented in
docs/guides/development-workflow.md; reviews should flag commits that violate the one-issue-one-worktree split.
Review Priorities
CRITICAL (Block merge)
- Security: path traversal, unsafe command construction, unbounded input, exposed secrets, or raw Agent Hook payload persistence
- Data loss: ignored write/transaction errors, incomplete rollback, or unsafe cross-database publication
- Runtime authority drift: duplicated MCP/Hook validation, a proxy that opens daemon state directly, or an Adapter fallback to a retired executable
IMPORTANT (Requires discussion)
- Missing test coverage for new behavior and failure paths
- Lock ordering, cancellation, blocking work, and transaction ownership are unclear
- Cross-platform correctness (HOME vs USERPROFILE, path separators, build target vs host OS)
SUGGESTION (Non-blocking)
- Naming clarity, code simplification
Active runtime conventions
cargo fmt --all --check,cargo test --workspace, and daemon clippy gates must pass.- The resident daemon is the only owner of SQLite, model state, and background workers.
clumsiesd mcp serveand_agentmodes are short-lived stdio/Hook proxies; they use typed XPC and must not constructDaemonState.- MCP schemas, argument validation, and domain conversion live in Rust. Do not add an untyped JSON tunnel.
- Proxy stdout is protocol-only. Diagnostics go to bounded, privacy-safe logging.
- Agent Hook normalization must discard prompt, transcript, assistant, and tool payloads before IPC.
- Adapter entries must point to the signed bundled
clumsiesd; no PATH, worktree build, or archived CLI fallback is allowed.
Retired Zig history
The former Zig CLI source is intentionally absent from the active tree. Its
last active snapshot remains recoverable from Git commit
4b18f7947a977dbc6b62f560b698dc992597f19d. Do not import or reuse that code
as an active compatibility layer without an explicit product migration.
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.
- today First seen · 43 lines · 513 tokens per session scan A a222a90193ed
clumsies copilot-instructions.md is an instructions file published in the GitHub repository lilhammerfun/clumsies (17 stars, last pushed 4d ago), licensed MIT. It adds 513 tokens to every session, about $0.0026 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-09-06.
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.
vscode buildNext.instructions.md
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
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
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.
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
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.