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/tta-lab/ttal-cli/claude-mdgit clone --depth 1 https://github.com/tta-lab/ttal-cliWrote 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/tta-lab/ttal-cli/claude-md)<a href="https://agentmods.dev/instructions/tta-lab/ttal-cli/claude-md"><img src="https://agentmods.dev/badge/instructions/tta-lab/ttal-cli/claude-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.03357 | $0.03357 |
| Opus 5 | $0.01679 | $0.01679 |
| Sonnet 5 | $0.00671 | $0.00671 |
| Haiku 4.5 | $0.00336 | $0.00336 |
Grade A, and why
ttal-cli CLAUDE.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 3d 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
TTAL is a CLI tool for coordinating agents, workers, messaging, and pipeline execution. Projects come from the standalone project CLI; durable plans and research live in FlickNote. Existing worker pipelines still use Taskwarrior internally.
Essential Commands
Development Workflow
# Format, tidy, lint, and build
make all
# Run all CI checks (lint, test, build)
make ci
# Run tests
make test
# Build binary
make build
# Install to GOPATH/bin
make install
Running the CLI
# Build and run with arguments
project list
# Or use the built binary directly
project list
Releasing
Tag a version to trigger the release workflow:
og git tag v0.1.0
GoReleaser builds binaries, creates a GitHub release, and pushes the
Homebrew formula to tta-lab/homebrew-ttal. Users upgrade via brew upgrade ttal.
Requires HOMEBREW_TAP_TOKEN secret in GitHub repo settings (a PAT with repo scope on the tap repo).
Architecture
Project Storage — TOML File
Projects are stored in a plain TOML file at ~/.config/ttal/projects.toml. No database dependencies.
Store Access: internal/project/resolve.go delegates to the project CLI.
TOML Format:
# Active projects are top-level sections
[ttal]
name = "TTAL Core"
path = "/Users/neil/Code/guion-opensource/ttal-cli"
[clawd]
name = "Clawd Workspace"
path = "/Users/neil/clawd"
# Archived projects go under [archived]
[archived.old-project]
name = "Legacy Thing"
path = "/old/path"
The table key IS the alias. Active projects are top-level [alias], archived under [archived.alias].
Project Resolution (internal/project/resolve.go):
// Resolution order for taskwarrior project matching:
// 1. Exact alias match (with "." hierarchical fallback)
// 2. Contains fallback ("ttal-cli" matches alias "ttal")
// 3. If no match → returns ""
path := project.ResolveProjectPath("ttal.pr")
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.
- 3d ago First seen · 317 lines · 3,357 tokens per session scan A 75d6caafcfd3
ttal-cli CLAUDE.md is an instructions file published in the GitHub repository tta-lab/ttal-cli (23 stars, last pushed 1mo ago), licensed MIT. It adds 3,357 tokens to every session, about $0.0168 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
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).
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.
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.