Borrowing it
Nothing to install: this file belongs to KyaniteHQ/linctl. 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/KyaniteHQ/linctl/master/AGENTS.mdgit clone --depth 1 https://github.com/KyaniteHQ/linctlWrote 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/kyanitehq/linctl/agents-md)<a href="https://agentmods.dev/instructions/kyanitehq/linctl/agents-md"><img src="https://agentmods.dev/badge/instructions/kyanitehq/linctl/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/kyanitehq/linctl/agents-md"><img src="https://agentmods.dev/badge/instructions/kyanitehq/linctl/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.00465 | $0.00465 |
| Opus 5.5 | $0.00186 | $0.00186 |
| Sonnet 5.5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
linctl 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 24d 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
AGENTS.md
linctl is a schema-aligned Go CLI — a Linear control surface for agent-safe coordination: free reads, target-pinned guarded writes.
Domain language — read before naming anything
@CONTEXT.md
Use these exact terms. Never say "workspace" (it is a Pinned/Resolved Target), never treat a Cycle as a "Sprint" mutation (Sprint is a read-only alias), always write ProjectMilestone in full. Each command's GraphQL backing is mapped in docs/internal/domain-map.md; named test flows are in docs/internal/test-scenarios.md.
Guarded writes fail closed on Target Mismatch — a hard stop, never a soft warning. Do not add bypass flags or relax the write guard (internal/client/write_guard.go).
Build / test / lint (go-task)
Run repository tasks through the pinned Go tool dependency: go tool task <task>.
go tool task ci— local gate before any PR.go tool task coverage— enforces 100% hand-written statement coverage for product code. Not part oftask ci; run it separately and keep new product code fully covered.go tool task fmt— gofumpt + goimports (NOT plain gofmt); this is the mutating formatter.
Generated GraphQL client
internal/client/internal/gql/generated.go is generated by genqlient from internal/client/operations/*.graphql via go generate ./.... Regenerate and commit it whenever operations change — CI fails on drift. When adding operations, refresh the vendored schema first with LINCTL_LINEAR_SDK_REF=master go tool task schema-refresh, or take an open chore/schema-refresh PR (CONTRIBUTING.md), then run go generate ./....
Live & integration tests
- Integration tests are build-tag gated and do NOT run under plain
go test ./...:go test -count=1 -tags=integration ./internal/client. - Never run write tests against real Linear data. Test resources use a
linctl-it-<runid>prefix and are closed/archived in cleanup. Never print or log secrets; report auth material assetormissing.
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.
- 24d ago Changed · -5 lines · -212 tokens per session 3a7ba0398f42
- 28d ago First seen · 34 lines · 677 tokens per session scan A f179dd2ec125
linctl AGENTS.md is an instructions file published in the GitHub repository KyaniteHQ/linctl (12 stars, last pushed yesterday), licensed MIT. It adds 465 tokens to every session, about $0.0019 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-09-25.
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.