Borrowing it
Nothing to install: this file belongs to augchan42/inkstone. 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/augchan42/inkstone/main/AGENTS.mdgit clone --depth 1 https://github.com/augchan42/inkstoneWrote 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/augchan42/inkstone/agents-md)<a href="https://agentmods.dev/instructions/augchan42/inkstone/agents-md"><img src="https://agentmods.dev/badge/instructions/augchan42/inkstone/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.02834 | $0.02834 |
| Opus 5 | $0.01417 | $0.01417 |
| Sonnet 5 | $0.00567 | $0.00567 |
| Haiku 4.5 | $0.00283 | $0.00283 |
Grade A, and why
inkstone 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 7d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to coding agents (Claude Code, opencode, and other Agent Skills–compatible tools) when working with code in this repository. CLAUDE.md is a symlink to this file.
What This Is
Inkstone (硯台) is a Claude Code plugin — a collection of agent skills for creative and design workflows. It is installed via the Claude Code plugin marketplace (/plugin marketplace add augchan42/inkstone). There is no build step and no dependencies to install. The repo is almost entirely Markdown skill definitions, plus one piece of runtime shell: a Stop hook (hooks/) that enforces the plan-review-loop skill's lifecycle.
Repository Structure
.claude-plugin/
plugin.json # Plugin manifest — name, version, "skills": "./skills"
marketplace.json # Marketplace listing metadata
hooks/
hooks.json # Auto-discovered by Claude Code — registers the Stop hook
stop-hook.sh # Enforces plan-review-loop completion; no-op when no loop is active
skills/
<skill-name>/
SKILL.md # Skill definition (frontmatter + instructions)
*.md # Optional reference files loaded by the skill
examples/
prompt-examples.md # Validated reference prompts for ink painting & tech-noir modes
hkoscon-2026/
hkoscon-2026-talk.html # Self-contained static talk deck + image assets
DEPLOY.md # How to (re)deploy the deck to Vercel
How Skills Work
Each skill is a SKILL.md with YAML frontmatter (name, description, user-invocable, argument-hint) followed by the full instruction set that Claude Code receives when the skill is invoked. Skills have no runtime code — they are prompt engineering documents that define behavior through instructions, examples, and rules.
When a skill has companion reference files (e.g., blakean-scene/blakean-reference.md, ui-ux-architect/audit-dimensions.md), the SKILL.md instructs the agent to read them at execution time.
Adding a New Skill
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.
- 7d ago First seen · 109 lines · 2,834 tokens per session scan A e3f1a5aceb1a
inkstone AGENTS.md is an instructions file published in the GitHub repository augchan42/inkstone (4 stars, last pushed 11d ago), licensed MIT. It adds 2,834 tokens to every session, about $0.0142 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
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).
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.
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 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).
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.