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/piebald-ai/tweakcc/agents-mdgit clone --depth 1 https://github.com/Piebald-AI/tweakccWrote 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/piebald-ai/tweakcc/agents-md)<a href="https://agentmods.dev/instructions/piebald-ai/tweakcc/agents-md"><img src="https://agentmods.dev/badge/instructions/piebald-ai/tweakcc/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 | $0.00880 | $0.00880 |
| Opus 5 | $0.00440 | $0.00440 |
| Sonnet 5 | $0.00176 | $0.00176 |
| Haiku 4.5 | $0.00088 | $0.00088 |
Grade A, and why
tweakcc 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 4d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This document provides guidelines for agentic coding assistants working in this repository.
Development Commands
# Build
pnpm build # Production build (typecheck + minify)
pnpm build:dev # Development build (no minification)
pnpm watch # Watch mode for iterative development
# Testing
pnpm test # Run all tests once
pnpm test:dev # Run tests in watch mode
npx vitest run <test-file> # Run single test file
pnpm run test -- <pattern> # Run tests matching pattern
# Linting & Formatting
pnpm lint # Typecheck + ESLint
pnpm format # Format code with Prettier
# Run CLI
pnpm start # Run built CLI
node dist/index.mjs # Alternative run command
Making changes
Whenever you make a logical change that belongs in one commit, update the changelog at the bottom of the "Unreleased" section. It should follow the format Change description (#PR) - @author. The change description should usually be the PR title unless there are multiple logical changes in the same PR that each deserve their own item.
Imports
// Group imports in this order:
import fs from 'node:fs/promises'; // Node.js built-ins (use node: prefix)
import path from 'node:path';
import chalk from 'chalk'; // Third-party libraries
import ink from 'ink';
import { getConfig } from '@/config'; // Internal imports (use @/ alias)
import { PatchConfig } from '@/types';
TypeScript
- Strict mode enabled in tsconfig.json
- Avoid
any: Useunknownwith type guards oras unknown as Typefor assertions - Interfaces for complex objects, types for simple unions
- Custom errors: Extend
Errorclass withnameproperty
export class CustomError extends Error {
constructor(message: string) {
super(message);
this.name = 'CustomError';
}
}
Naming Conventions
- Files: camelCase for logic (
config.ts), PascalCase for React components (MainView.tsx) - Functions: camelCase (
getConfig,detectInstallation) - Constants: UPPER_SNAKE_CASE (
CONFIG_DIR,DEFAULT_CONFIG) - Components: PascalCase with descriptive names (
ThinkingVerbsView) - Interfaces: PascalCase, descriptive (
StringsPrompt,MarkdownPrompt)
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.
- 4d ago First seen · 120 lines · 880 tokens per session scan A 83b05980cac8
tweakcc AGENTS.md is an instructions file published in the GitHub repository Piebald-AI/tweakcc (2,479 stars, last pushed yesterday), licensed MIT. It adds 880 tokens to every session, about $0.0044 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.
Other instructions, from other repositories
html-anything AGENTS.md
AGENTS.md instructions for nexu-io/html-anything, covering this is not the next.js you know, workspace shape and commands.
framework AGENTS.md
AGENTS.md instructions for ai-driven-dev/framework, covering agents.md, behavior, communication, action and memory management.
claude-code-profiles CLAUDE.md
Instructions for quinnjr/claude-code-profiles, covering claude.md, project, architecture, command interface and directory-local profiles.
autogen copilot-instructions.md
Copilot instructions for microsoft/autogen, covering autogen multi-agent ai framework, working effectively, prerequisites and environment setup, python development workflow and quick validation (under 1 second each).
toh-framework CLAUDE.md
Claude Code instructions for wasintoh/toh-framework, covering claude.md — toh framework (repo development guide), what this is, everyday commands, verification protocol and single source, transformed per ide.
jentic-one GEMINI.md
Instructions for jentic/jentic-one: Otherwise, read AGENTS.md — this repo's canonical agent guidance.