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.
npx agentmods add instructions/parkviewlab/flint-slating/agents-mdgit clone --depth 1 https://github.com/ParkviewLab/flint-slatingWhat 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 | $0.00502 | $0.00502 |
| Opus 5 | $0.00251 | $0.00251 |
| Sonnet 5 | $0.00100 | $0.00100 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
flint-slating 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 yesterday.
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.
This is a copy
100% identical to ebony-enriching AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
ParkviewLab conventions
This repo follows the ParkviewLab handbook —
the single source of truth for how we work. These pointer files don't re-inline its rules:
read the handbook before non-trivial work, starting with
ai-collaboration.md
(the behavioural contract). Only the safety-critical guardrails are summarized here.
If present, read docs/northstar.md before working. It states the project's intent and is authoritative.
Shared-state writes need explicit authorization
- Merging a PR into
developis the user's call. A broad directive ("fix all that", "finish it") authorizes work on the branch, not the merge. - Tagging, cutting a release, force-pushing, or pushing to a protected branch each need an explicit, per-action go-ahead — never inferred from a descriptive label (e.g. "→ v0.1.1"). One release ask covers the whole CLI release flow.
Workflow basics
- Work in an ephemeral, prefixed worktree off
develop(feature-/fix-/doc-/…) — don't commit ondevelop/maindirectly. Open a PR intodevelop. - PRs are squash-merged, so the PR title carries the Conventional Commit prefix (
feat:/fix:/docs:/…) the changelog is generated from.
Everything else lives in the handbook (don't rely on memory): branching, commits & changelogs, releases, Python tooling, CI, licensing, and the full communication norms — see https://github.com/ParkviewLab/handbook/tree/main/docs.
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.
- yesterday First seen · 30 lines · 502 tokens per session scan A 21470c25861c
flint-slating AGENTS.md is an instructions file published in the GitHub repository ParkviewLab/flint-slating (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 502 tokens to every session, about $0.0025 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ebony-enriching AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
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.
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).
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.
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).
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.