Borrowing it
Nothing to install: this file belongs to darinegan/chocolatey-packages. 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/darinegan/chocolatey-packages/master/AGENTS.mdgit clone --depth 1 https://github.com/darinegan/chocolatey-packagesWrote 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/darinegan/chocolatey-packages/agents-md)<a href="https://agentmods.dev/instructions/darinegan/chocolatey-packages/agents-md"><img src="https://agentmods.dev/badge/instructions/darinegan/chocolatey-packages/agents-md.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.00356 | $0.00356 |
| Opus 5 | $0.00178 | $0.00178 |
| Sonnet 5 | $0.00071 | $0.00071 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
chocolatey-packages AGENTS.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 8d 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.
What it actually says
Agent instructions
This repository currently lands a validate-only automation foundation.
Operating rules
- Keep pull request validation secret-free and fork-safe.
- Use
pull_requestfor validation; do not usepull_request_target. - Do not add secrets to pull request validation.
- Update and publish workflow design is deferred to issue #40.
- Keep #39 open as a child follow-up under that deferred stream.
- Use
ghto validate live repository controls before changing release automation. - Pin external GitHub Actions to full 40-character commit SHAs.
- Prefer
git, PowerShell, andghover third-party actions in jobs that use sensitive tokens. - Use GitHub Issues as durable work tracking for non-trivial changes.
- Link pull requests to the issues they resolve with closing references.
- When implementation discovers follow-up work, create a follow-up issue instead of leaving that work only in chat, comments, or local plans.
Documentation ownership
README.mdowns the user-facing overview.CONTRIBUTING.mdowns canonical human contributor, maintainer, and release instructions.AGENTS.mdowns agent behavior only.
Cross-reference these files instead of duplicating content. Do not turn automated repository controls into human maintainer chores in CONTRIBUTING.md; document only the manual effort that remains. If you learn durable repository behavior or change automation behavior, update the most appropriate document so the next human or AI agent has less to rediscover.
Self-documenting expectation
Leave the repository easier to understand than you found it. When automation changes, update the docs in the same change. When adding safeguards, make the invariant clear in workflow names, job names, and short comments where the reason is not obvious.
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.
- 8d ago First seen · 30 lines · 356 tokens per session scan A 15f4ed76d495
chocolatey-packages AGENTS.md is an instructions file published in the GitHub repository darinegan/chocolatey-packages (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 356 tokens to every session, about $0.0018 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
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.
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).
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).
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.
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.