Borrowing it
Nothing to install: this file belongs to yschimke/skills. 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/yschimke/skills/main/AGENTS.mdgit clone --depth 1 https://github.com/yschimke/skillsWrote 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/yschimke/skills/agents-md)<a href="https://agentmods.dev/instructions/yschimke/skills/agents-md"><img src="https://agentmods.dev/badge/instructions/yschimke/skills/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/yschimke/skills/agents-md"><img src="https://agentmods.dev/badge/instructions/yschimke/skills/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.01674 | $0.01674 |
| Opus 5.5 | $0.00670 | $0.00670 |
| Sonnet 5.5 | $0.00335 | $0.00335 |
| Haiku 4.5 | $0.00167 | $0.00167 |
Grade A, and why
skills 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 18d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI agents (Claude Code, Codex, Gemini, etc.) working in this repo.
This is a content-only repo. The skills here are markdown documentation
that pairs with the compose-preview CLI and Gradle plugin published from
yschimke/compose-ai-tools.
The CLI lives there; consumer guidance lives here.
Generic skills, not harness wiring. Skills here read the same in any agent
host: what to do, and which MCP tools or CLI commands to use. The set is meant
to grow beyond the preview toolchain into a wider range of Compose and Android
UI skills. Anything that names a particular host, or installs into, configures
or works around one (per-harness manifests, MCP client config, hooks, host
detection, a host's cloud sandbox, claude.yml sessions), belongs in
yschimke/compose-agent-plugins.
The full table, and the references still waiting to move, are in its
docs/repository-consolidation.md.
Don't add new host-specific material here.
Two upstream repos, not one. The CLI, the Gradle plugin, the renderers and
the local daemon MCP ship from compose-ai-tools. The preview server —
everything behind compose-preview serve, including its catalog MCP endpoint,
the UI builder and the playground — ships from
yschimke/compose-preview-server,
on its own release line. When a skill cites serve source or a server-side
design doc, it belongs to that repo. (Its operator-facing manual,
docs/public-preview-server.md, still lives in compose-ai-tools — cite it
where it actually is rather than where the code is.)
Git history
- Git history attributes work only to the human committer. Never add an AI
Co-authored-by:trailer or use an agent identity as author or committer, in a commit or in a PR title or body. Session links and "Generated with" footers are fine. - Human reviewers: verify before reporting an attribution finding. Automated reviewers do
not report attribution at all; see Review guidelines. Across these
repositories it is the most-reported and least-real review finding, and reports have named
commits that do not exist. Never infer the identity from the fact that an agent wrote the code: it
is whatever
git config user.emailheld, and here that is the human. Check the real range first:
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.
- 18d ago Changed · +2 lines · +35 tokens per session 2e6fe81f23d6
- 24d ago Changed · +42 lines · +725 tokens per session bb84a4081d7a
- 27d ago Changed · +11 lines · +211 tokens per session 1dd2f9b5494f
- 1mo ago Changed · +10 lines · +148 tokens per session af69579dfc40
- 2mo ago First seen · 52 lines · 555 tokens per session scan A e75f593fb557
skills AGENTS.md is an instructions file published in the GitHub repository yschimke/skills (2 stars, last pushed 14d ago), licensed Apache-2.0. It adds 1,674 tokens to every session, about $0.0067 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.