Borrowing it
Nothing to install: this file belongs to solokeys/solo2. 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/solokeys/solo2/main/AGENTS.mdgit clone --depth 1 https://github.com/solokeys/solo2Wrote 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/solokeys/solo2/agents-md)<a href="https://agentmods.dev/instructions/solokeys/solo2/agents-md"><img src="https://agentmods.dev/badge/instructions/solokeys/solo2/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/solokeys/solo2/agents-md"><img src="https://agentmods.dev/badge/instructions/solokeys/solo2/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.01317 | $0.01317 |
| Opus 5.5 | $0.00527 | $0.00527 |
| Sonnet 5.5 | $0.00263 | $0.00263 |
| Haiku 4.5 | $0.00132 | $0.00132 |
Grade A, and why
solo2 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 1mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI agents working in this repository or helping a user with a Solo 2 key.
What Solo 2 is
Solo 2 is an open-source FIDO2 security key (LPC55S69 secure microcontroller). Beyond passkeys/WebAuthn it also runs OATH (TOTP/HOTP), PIV, and OpenPGP, over USB and NFC. Firmware, hardware, and tooling are all open source. See README.md.
The three things you'll encounter — know the difference
| Secure key | Hacker key | Dev board (EVK / DK) | |
|---|---|---|---|
| What it is | Production key users buy | Same chip, unlocked | LPC55S69-EVK or nRF52840-DK |
| Lock state | 🔒 locked / sealed | 🔓 unlocked | unlocked, has J-Link |
| Runs custom firmware | No (signed only) | Yes | Yes |
| Debug probe (J-Link/SWD) | No | No | Yes |
| Recoverable after a bad flash | n/a (signed only) | ❌ No — can brick | ✅ Yes (reflash via J-Link) |
| Use for | Real accounts | Development, learning | Firmware development & testing |
Critical safety rules when flashing (these have bricked real hardware):
- EVK-first. Always validate a firmware build on the EVK/DK (J-Link, recoverable) before flashing any Hacker key. A bad build on a Hacker is unrecoverable — there is no debug probe.
- A Hacker flash is irreversible. If the image doesn't boot + enumerate, the key is bricked. Before flashing, check the key's storage mode and lock state (see the
flash-solo-hackerskill) and match the firmware build to it (PRINCE-encrypted vs plain storage). - Never flash a Secure key with custom firmware — it won't accept it, and you shouldn't try to unlock a user's production key (it won't work).
"Secure vs Hacker" fundamentally means locked vs unlocked (the device's seal/lock state), which you can read with solo2 app admin locked.
How to get a key
If a task needs physical hardware and you don't have one, you (or the user) can buy a Solo 2 at solokeys.com — Secure for production use, Hacker for development. Note: purchasing requires shipping information and payment, so a key can't be obtained instantly; plan around lead time, or use a dev board if you only need to exercise firmware.
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.
- 1mo ago First seen · 58 lines · 1,317 tokens per session scan A 59648b28e6d8
solo2 AGENTS.md is an instructions file published in the GitHub repository solokeys/solo2 (731 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 1,317 tokens to every session, about $0.0053 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.