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/intelligencedev/manifold/agents-mdgit clone --depth 1 https://github.com/intelligencedev/manifoldWhat 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.02315 | $0.02315 |
| Opus 5 | $0.01157 | $0.01157 |
| Sonnet 5 | $0.00463 | $0.00463 |
| Haiku 4.5 | $0.00231 | $0.00231 |
Grade A, and why
manifold 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- manifold CLAUDE.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go/manifold
Coding Conventions
Project Structure & Module Organization
Source lives in internal/ (e.g., internal/agent, internal/orchestrator); keep new packages focused on one concern and avoid import cycles. CLI/Server entrypoints sit under cmd/ with binaries for the agent, HTTP server (manifold, implemented in cmd/agentd), and embedctl (if present). Docs reside in docs/, assets in assets/, and deployment scaffolding in docker/, configs/, and top-level example.env. Co-locate tests with their packages and share fakes through internal/testhelpers.
Package Organization
- Keep packages small and focused on a single responsibility.
- Avoid cyclical dependencies; extract interfaces when necessary.
Dependency Injection
- Promote testability via interface‑driven design.
- Use constructor functions (e.g.,
NewService(...)) to inject dependencies.
Concurrency
Follows Go's concurrency mantra: "Don't communicate by sharing memory; share memory by communicating." The channel becomes the synchronization point.
Essential Go CLI Tools
The following Go command-line tools are essential for development, testing, and maintenance in this project. Use them as described to ensure code quality and consistency:
| Tool | Purpose |
|---|---|
go build |
Compiles packages and their dependencies into an executable. |
go run |
Compiles and runs the specified Go program. |
go fmt |
Formats Go source code according to the language's style guidelines. |
gofmt |
Standalone formatter; also available as an executable. |
go test |
Runs tests and benchmarks. Use -coverprofile with go tool cover to analyze test coverage. |
go vet |
Examines Go source code and reports suspicious constructs that could be bugs. |
go doc |
Extracts and generates documentation for Go packages. |
go get |
Adds, updates, or removes dependencies in the go.mod file. |
go mod |
Provides access to module operations (e.g., go mod tidy to clean up dependencies). |
go tool |
Runs the specified Go tool (see below for examples). |
cgo |
Enables the creation of Go packages that call C code. |
pprof |
For profiling Go programs. |
fix |
Rewrites Go programs that use old language and library features. |
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.
- 2d ago First seen · 171 lines · 2,315 tokens per session scan A b71c212722b2
manifold AGENTS.md is an instructions file published in the GitHub repository intelligencedev/manifold (497 stars, last pushed 25d ago), licensed MIT. It adds 2,315 tokens to every session, about $0.0116 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
go-micro CLAUDE.md
Instructions for micro/go-micro, covering claude.md - go micro project guide, project overview, build & test, run all tests and run tests for a specific package.
go-micro AGENTS.md
Instructions for micro/go-micro, covering repository agent instructions and pull requests from codex tasks.
jwx AGENTS.md
AGENTS.md instructions for lestrrat-go/jwx, covering agents.md, for module consumers, go version, goexperiment and module path vs physical layout.
azure-sdk-for-go go-examples.instructions.md
Instructions for Azure/azure-sdk-for-go, a project described as: This repository is for active development of the Azure SDK for Go. For consumers of the SDK we recommend visiting our public developer docs at.
azure-sdk-for-go copilot-instructions.md
Copilot instructions for Azure/azure-sdk-for-go, covering generated code — do not suggest changes, prerequisites, local sdk generation and package lifecycle (typespec), authoritative reference and default behaviors.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.