Borrowing it
Nothing to install: this file belongs to liliang-cn/tagit. 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/liliang-cn/tagit/main/AGENTS.mdgit clone --depth 1 https://github.com/liliang-cn/tagitWrote 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/liliang-cn/tagit/agents-md)<a href="https://agentmods.dev/instructions/liliang-cn/tagit/agents-md"><img src="https://agentmods.dev/badge/instructions/liliang-cn/tagit/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.00602 | $0.00602 |
| Opus 5 | $0.00301 | $0.00301 |
| Sonnet 5 | $0.00120 | $0.00120 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
tagit 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 8d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This repository is currently design-first. The top-level architecture and system constraints live in DESIGN.md. Detailed implementation contracts are under docs/:
docs/domain-schema-spec.md: artifact and domain contractsdocs/state-machine-spec.md: lifecycle and recovery rulesdocs/backend-module-design.md:tagitdmodule boundaries
When code is added, keep Go packages under internal/ with module-aligned directories such as internal/domain, internal/events, internal/store, internal/runtime, and internal/scheduler.
Build, Test, and Development Commands
The repository does not yet contain executable code. Once bootstrapped, prefer these commands:
go test ./...
go test ./internal/...
go build ./...
Use go test ./... for full validation, go test ./internal/... for package-scoped iteration, and go build ./... to catch interface and wiring regressions.
Coding Style & Naming Conventions
Write Go in standard gofmt style with tabs for indentation. Keep package names short and lowercase: store, policy, runtime. Exported types use PascalCase; unexported helpers use camelCase. Interface names should reflect capability, such as EventStore, Supervisor, or Broker.
Name documents and specs in kebab-case, for example domain-schema-spec.md. Keep terminology aligned with the existing specs: ArtifactEnvelope, ExecutionPlan, FailedRecoverable.
Testing Guidelines
Use Go’s built-in testing package. Prefer table-driven tests for domain validation, policy rules, and state transitions. Name files *_test.go and test functions TestXxx. Add focused unit tests for pure logic first, then integration tests for PTY, worktree, and persistence boundaries.
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.
- 8d ago First seen · 49 lines · 602 tokens per session scan A d6796726a7fd
tagit AGENTS.md is an instructions file published in the GitHub repository liliang-cn/tagit (5 stars, last pushed 2d ago), licensed MIT. It adds 602 tokens to every session, about $0.0030 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
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.
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).
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).
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.
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.