agentmods.dev

linctl AGENTS.md

An agent instruction file for linctl, a command-line tool. It sets rules for small tested changes, documentation updates, release checks, and tests for CLI and GraphQL changes.

In plain words
What is it for?
Use it when changing linctl commands, GraphQL operations, release versioning, Homebrew or Nix support, or the master API reference.
Why use it?
It keeps code, documentation, package releases, and API behavior aligned while preventing unnecessary rewrites or unverified changes.

Instructions file for CodexOpenCode

145 9d ago A scan 653 tokens original MIT
View the source file dorkitude/linctl
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/dorkitude/linctl/agents-md
Clone the repo
git clone --depth 1 https://github.com/dorkitude/linctl

Made for: Codex, OpenCode.

Per session 653 This file is loaded in full into every session.
When invoked 653 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00653 $0.00653
Opus 5 $0.00327 $0.00327
Sonnet 5 $0.00131 $0.00131
Haiku 4.5 $0.00065 $0.00065

Measured 2d ago against content hash 415b5766a6a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

AGENTS.md · 47 lines

How it starts

The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Purpose

Ship safe, small, tested changes to linctl with docs that match behavior.

Operating Rules

  • Keep patches minimal and focused; avoid drive-by refactors.
  • Prefer rg/go test/existing scripts; do not invent parallel tooling.
  • Never rewrite user-authored history (reset --hard, force-push) unless explicitly requested.
  • If behavior changes, update docs in the same PR (README.md, SKILL.md, as needed).
  • If a change updates release versioning, do not consider it complete until Homebrew tap bump status and Nix installability are verified.

Quality Bar

  • Run: go test ./... before finalizing code changes.
  • For CLI flag/command changes, add or update command tests in cmd/*_test.go.
  • For GraphQL query/mutation changes, add or update API tests in pkg/api/*_test.go.
  • If tests are skipped, state exactly what was skipped and why.

Docs Freshness

  • Treat master_api_ref.md as drift-prone; verify against current official Linear docs before editing claims (auth, scopes, rate limits, headers, deprecations).
    • When you identify drift around your feature area, edit master_api_ref.md in the same PR as your feature.
  • Prefer exact terms from upstream docs; avoid hardcoded limits unless sourced.
  • Keep examples runnable with current CLI.

Fast Checks

  • linctl --version
  • linctl --help
  • go test ./...

Release + Package Managers (Owners Only)

  • Owners cut releases from master using semver tags vX.Y.Z.
  • Required for auto Homebrew bump: repo secret HOMEBREW_TAP_TOKEN (write access to dorkitude/homebrew-linctl).
  • Version bump policy: release/version bumps must include Homebrew and Nix verification in the same workstream.
    • Homebrew verification means auto workflow success plus merged tap PR, or a merged manual tap bump PR.
    • Nix verification means the flake builds from the release tag, or the blocker is explicitly documented when Nix is unavailable in the release environment.
  • Flow:
    1. git push origin master
    2. git tag -a vX.Y.Z -m "vX.Y.Z: <summary>" && git push origin vX.Y.Z
    3. gh release create vX.Y.Z --title "linctl vX.Y.Z" --notes "..."
    4. Verify Bump Homebrew Tap workflow succeeds.
    5. Merge bump PR in dorkitude/homebrew-linctl (close stale bump PRs).
    6. Confirm formula points to new tag+sha and brew upgrade linctl resolves.
    7. Confirm Nix installability from the tag: nix build github:dorkitude/linctl/vX.Y.Z nix profile install github:dorkitude/linctl/vX.Y.Z linctl --version

Read the full file on GitHub · 47 lines

Changes

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.

  1. 2d ago First seen · 47 lines · 653 tokens per session scan A 415b5766a6a8

Subscribe to this mod's changes

linctl AGENTS.md is an instructions file published in the GitHub repository dorkitude/linctl (145 stars, last pushed 9d ago), licensed MIT. It adds 653 tokens to every session, about $0.0033 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-30.

Backend and APIsGit and workflowTesting
Related

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.

openai/codex · 5,182 tokens

buildNext

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).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

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).

microsoft/vscode · 5,001 tokens

spec-kit 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.

github/spec-kit · 7,040 tokens

langchain 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.

langchain-ai/langchain · 4,345 tokens