Borrowing it
Nothing to install: this file belongs to PascaleBeier/hitkeep. 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/PascaleBeier/hitkeep/main/AGENTS.mdgit clone --depth 1 https://github.com/PascaleBeier/hitkeepWrote 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/pascalebeier/hitkeep/agents-md)<a href="https://agentmods.dev/instructions/pascalebeier/hitkeep/agents-md"><img src="https://agentmods.dev/badge/instructions/pascalebeier/hitkeep/agents-md/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/instructions/pascalebeier/hitkeep/agents-md"><img src="https://agentmods.dev/badge/instructions/pascalebeier/hitkeep/agents-md.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.03018 | $0.03018 |
| Opus 5.5 | $0.01207 | $0.01207 |
| Sonnet 5.5 | $0.00604 | $0.00604 |
| Haiku 4.5 | $0.00302 | $0.00302 |
Grade A, and why
hitkeep 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 5d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HitKeep Agent Guide
This file is public guidance for AI-assisted contributions to HitKeep. It is written for external contributors, maintainers, and coding agents working from the open-source repository.
CLAUDE.md is a compatibility bridge for Claude Code. Keep AGENTS.md as the canonical public instruction file and avoid duplicating the full guide in multiple places.
Start Here
- Treat the current repository as the source of truth. If an issue, prompt, or older document disagrees with the code, inspect the code first.
- Use
./hkas the workflow source of truth, but consume that truth through the callable central developer MCP tools on its compact surface whenever they cover the task. Reserve direct CLI discovery for MCP bootstrap or repair, explicitly approved fallback, and workflows intentionally absent from MCP such as source rewrites; never copy commands, runtime configuration facts, build tags, cloud defaults, ports, tool versions, or QA gates into instructions. - Treat developer MCP as available only when the relevant
hk_*tools are exposed and a read-only call succeeds; a configured or enabled host entry is not proof. Register one long-lived clone's locally built./hklauncher once, query./hk mcp manifest --output jsononly for the live bootstrap contract, and verify the returned workspace ID against the configured fallback or server catalog. If tools are absent or fail, inspect host MCP health, compare the registration with the manifest, report whether registration, startup, workspace routing, or task reload is blocking use, and obtain explicit user approval before invoking an equivalent versioned./hk --output jsonaction. When that fallback is approved,./hk catalog configuration --output jsonis the structured runtime configuration documentation contract. Existing tasks may require a host reload before newly registered tools appear; reserve human output for people. - Inspect the current workspace before setup, services, builds, or QA. Reuse an active run instead of starting duplicate work.
- Development is one container-only session per workspace. It has status and event cursors, not a run ID. Setup, QA, builds, and smokes remain finite runs.
- Use the developer CLI's formatter and Go migration surfaces for deliberate source rewrites. QA and MCP checks must remain non-mutating.
- Keep changes small and tied to the user-visible behavior or maintenance task being requested.
- Do not include credentials, customer data, private deployment details, local machine paths, or screenshots that reveal private analytics.
- Preserve HitKeep's product shape: one deployable application, clear operator controls, and no unnecessary service dependencies.
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.
- 5d ago Changed · +20 tokens per session 2de9604f0c49
- 28d ago Changed · -12 tokens per session ea79c148b69a
- 1mo ago First seen · 146 lines · 3,010 tokens per session scan A a95077ce0541
hitkeep AGENTS.md is an instructions file published in the GitHub repository PascaleBeier/hitkeep (98 stars, last pushed 4d ago), licensed MIT. It adds 3,018 tokens to every session, about $0.0121 per session on Opus 5.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-30.
Other instructions, from other repositories
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.