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/ivanlutsenko/awac-ai-agent-plugins/claude-mdgit clone --depth 1 https://github.com/IvanLutsenko/awac-ai-agent-pluginsWrote 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/ivanlutsenko/awac-ai-agent-plugins/claude-md)<a href="https://agentmods.dev/instructions/ivanlutsenko/awac-ai-agent-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/ivanlutsenko/awac-ai-agent-plugins/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.00915 | $0.00915 |
| Opus 5 | $0.00458 | $0.00458 |
| Sonnet 5 | $0.00183 | $0.00183 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
awac-ai-agent-plugins 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 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Plugin Marketplace
Active Plugins
- crashlytics (v4.4.4) — Multi-platform crash analysis with git blame forensics
- obsidian-tracker (v4.5.2) — Project tracking, task management, session logging via Obsidian
- locale-notifications (v2.0.1) — macOS notifications in system language
- combined-review (v1.4.0) — Multi-agent code review + CodeRabbit CLI; GitHub PR + GitLab MR with inline resolvable threads
- clip-maker (v1.3.1) — Automated vertical clip creator (whisper + Claude + ffmpeg)
- drawbridge (v0.1.1) — Bridge briefs to image-gen web UIs (Gemini/ChatGPT/Grok/Midjourney), per-target prompt tuning
- plugin-cross-port (v0.10.1) — Bidirectional CC ↔ Codex plugin conversion (agents → standalone Codex skills)
- auto-theme (v1.1.2) — Syncs Claude Code + Codex themes with macOS light/dark; bundles gruvbox-light / sunset-drive
Plugin Structure
plugins/{name}/
├── .claude-plugin/plugin.json # Manifest
├── .mcp.json # Optional MCP servers
├── commands/*.md # Slash commands
├── agents/*.md # Agents
└── standards/*.md # Knowledge base
Command Format
---
description: Shown in /help
argument-hint: "path/to/file"
allowed-tools: ["Read", "Write", "Bash"]
---
Instructions for Claude...
Agent Format
---
name: agent-name
description: Role description
tools: Read, Write, Bash
model: sonnet
---
System prompt...
Development
# Create plugin
mkdir -p plugins/{name}/{.claude-plugin,commands,agents}
# Test locally
/plugin install ./plugins/{name}
# Publish
git add . && git commit -m "feat(name): desc" && git push
Cross-Port Managed Plugins
Plugins attached through plugin-cross-port reconcile marketplace entries
automatically:
python3 plugins/plugin-cross-port/scripts/cross_port.py marketplace sync
python3 plugins/plugin-cross-port/scripts/cross_port.py marketplace check
For semantic gaps, use:
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 · 102 lines · 915 tokens per session scan A 1dcfdce8bb1e
awac-ai-agent-plugins CLAUDE.md is an instructions file published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 915 tokens to every session, about $0.0046 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-31.
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.