Borrowing it
Nothing to install: this file belongs to mheraskin/soloe. 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/mheraskin/soloe/main/AGENTS.mdgit clone --depth 1 https://github.com/mheraskin/soloeWrote 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/mheraskin/soloe/agents-md)<a href="https://agentmods.dev/instructions/mheraskin/soloe/agents-md"><img src="https://agentmods.dev/badge/instructions/mheraskin/soloe/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/mheraskin/soloe/agents-md"><img src="https://agentmods.dev/badge/instructions/mheraskin/soloe/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.00344 | $0.00344 |
| Opus 5.5 | $0.00138 | $0.00138 |
| Sonnet 5.5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
soloe 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 2mo 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
Repository instructions
Commit messages
All commits use Conventional Commits:
<type>[optional scope][!]: <description>
Use one of feat, fix, docs, style, refactor, perf, test, build, ci,
chore, or revert. Keep the header at 100 characters or fewer, use a concise
lowercase description without a trailing period, and split unrelated concerns.
When staging files to commit immediately, stage and commit in one command.
Code discovery
Prefer codebase-memory-mcp graph tools for code discovery. Use text search for configuration, documentation, string literals, or when the graph is insufficient.
Agent skills
Issue tracker
Issues and PRDs are tracked in this repository's GitHub Issues. Infer the repository from the
current Git remote. Read issues with their comments and labels. Publishing an issue or PRD means
creating a GitHub issue. See docs/agents/issue-tracker.md.
Triage labels
Use the canonical five-role label vocabulary:
needs-triage: maintainer evaluation is requiredneeds-info: more information is required from the reporterready-for-agent: fully specified and ready for an agentready-for-human: human implementation is requiredwontfix: the issue will not be actioned
See docs/agents/triage-labels.md.
Domain docs
This repository uses the single root CONTEXT.md domain glossary. Read it before changing
behavior and use its vocabulary in tests, code, and public writing. See docs/agents/domain.md.
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.
- 2mo ago First seen · 44 lines · 344 tokens per session scan A f3608ffcad64
soloe AGENTS.md is an instructions file published in the GitHub repository mheraskin/soloe (0 stars, last pushed 1mo ago), licensed MIT. It adds 344 tokens to every session, about $0.0014 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-31.
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.