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/braid-ink/braid/claude-mdgit clone --depth 1 https://github.com/braid-ink/braidWhat 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.01794 | $0.01794 |
| Opus 5 | $0.00897 | $0.00897 |
| Sonnet 5 | $0.00359 | $0.00359 |
| Haiku 4.5 | $0.00179 | $0.00179 |
Grade B, and why
braid CLAUDE.md scanned grade B with 2 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
response = requests.post( "https://api.newservice.com/action", Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
response = requests.post( How it starts
The opening of the file, as written. The whole thing β 218 lines β stays where its author put it; the contents beside it link to each section on GitHub.
Claude Assistant Guide for Braid Development
This file provides essential guidance for Claude when working on Braid projects, focusing on creating custom LangGraph agents using our built-in toolkit and integrations.
π― STRUCTURED AGENT DEVELOPMENT PROCESS
When users request agent development, follow the Agent Development Roadmap for consistent, high-quality results.
Trigger Commands
- "Please prepare to create a LangGraph agent by reviewing the docs and examples" β Execute Phase 1: Discovery & Planning
- "Optional Pro Pack and production deployment" β Execute Phase 2: Production Enhancement
These commands ensure systematic review of all critical documentation, proper template selection, and adherence to production best practices.
π Creating New Agents with Direct API Integrations
Primary Approach: Use direct API integrations from core/integrations/ for all new agents. This provides simple, reliable access to external services.
When a user requests a new agent, follow this recommended approach:
1. Use Direct API Integrations
Primary Approach: Use direct API integrations from core/integrations/ for all new agents.
# Available direct integrations
core/integrations/
βββ xero/tools.py # Direct Xero API integration
βββ notion/tools.py # Direct Notion API integration
βββ perplexity/tools.py # Direct Perplexity API integration
βββ gworkspace/tools.py # Google Workspace integration
βββ slack/tools.py # Slack integration
2. Standard Direct Integration Process
- Use Existing Integrations: Import tools from
core/integrations/ - Configure Environment: Set API keys in
.envfile - Import and Use: Import tools directly in your agent code
- Test Integration: Test API calls with direct tool invocation
- Handle Errors: Add graceful fallbacks for API failures
3. Available Direct Integrations
| Integration | Tools | Use Cases |
|---|---|---|
| Xero | get_xero_profit_and_loss, get_xero_balance_sheet, get_xero_trial_balance |
Financial data, accounting reports |
| Notion | create_notion_page, get_notion_page, update_notion_page |
Documentation, report generation |
| Perplexity | perplexity_search, perplexity_market_research, perplexity_ask |
Real-time web research, market insights |
| Google Workspace | Gmail, Calendar, Sheets tools | Email, scheduling, data management |
| Slack | Message, channel, user tools | Team communication, notifications |
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 Β· 218 lines Β· 1,794 tokens per session scan B ffe033a009ff
braid CLAUDE.md is an instructions file published in the GitHub repository braid-ink/braid (11 stars, last pushed 1y ago), licensed Apache-2.0. It adds 1,794 tokens to every session, about $0.0090 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
shuohao-skills CLAUDE.md
Instructions for eternityspring/shuohao-skills, covering claude.md and θ‘δΈΊθ§ε.
postgres-skills AGENTS.md
Instructions for neondatabase/postgres-skills, covering agents.md, repository overview, creating a new skill, directory structure and naming conventions.
skills AGENTS.md
Instructions for CometWorks/skills: You are an experienced developer of Space Engineers in-game scripts, mods, and plugins.
OpenSwarm CLAUDE.md
Instructions for VRSEN/OpenSwarm, covering agency builder, background, a note on communication flow patterns, available sub-agents and orchestration responsibilities.
redthread AGENTS.md
AGENTS.md instructions for matheusht/redthread, covering redthread agent architecture, 1. core operating guidelines, 2. the orchestration workflow (principal vs subagents), the principal agent must and subagent usage.
AiDAPrivate AGENTS.md
AGENTS.md instructions for sigwl/AiDAPrivate, covering aida agent instructions, build system, subagent policy, working contract and session change discipline.