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/fiale-plus/fiale-claude-plugins/claude-mdgit clone --depth 1 https://github.com/fiale-plus/fiale-claude-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/fiale-plus/fiale-claude-plugins/claude-md)<a href="https://agentmods.dev/instructions/fiale-plus/fiale-claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/fiale-plus/fiale-claude-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.01156 | $0.01156 |
| Opus 5 | $0.00578 | $0.00578 |
| Sonnet 5 | $0.00231 | $0.00231 |
| Haiku 4.5 | $0.00116 | $0.00116 |
Grade A, and why
fiale-claude-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 5d 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 — 145 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 when working with this repository.
Repository Overview
A Claude Code plugin marketplace with plugins that extend Claude's capabilities via terminal-accessible features: PR monitoring, calendar/Slack integration, music control, finance tracking, and custom alerts.
Testing
# Full test suite
plugins/claude-status-hub/tests/run-tests.sh
# Individual tests
bash plugins/claude-status-hub/tests/test-refresh-prs.sh
bash plugins/claude-status-hub/tests/test-slack.sh
bash plugins/claude-status-hub/tests/test-adaptive-intervals.sh
Tests use bash assertions (pass()/fail()), backup/restore production files, and use fixtures for mock data.
Architecture
Plugin Structure
plugins/
├── claude-status-hub/ # Primary plugin - statusline monitoring
│ ├── .claude-plugin/ # Plugin manifest (plugin.json)
│ ├── bin/ # Shell scripts (daemon, statusline, bridge)
│ ├── commands/ # User-facing commands (.md with YAML frontmatter)
│ ├── skills/ # Reusable workflows (.md files)
│ ├── hooks/ # Lifecycle hooks (hooks.json + refresh.sh)
│ └── tests/ # Test suite with fixtures
└── tradingview/ # Finance plugin - market screening via MCP
Data Flow
Bridge file architecture:
~/.claude/status-config.json- Persistent config (tracked items, connection settings)/tmp/status-hub.json- Real-time bridge read by statusline, written by daemon/skills/tmp/status-hub-error.txt- Error state for statusline display
Daemon Architecture
The background daemon (bin/refresh-daemon.sh) uses adaptive refresh intervals:
| Refresh Type | Base Interval | Ceiling (max idle) |
|---|---|---|
| Light (PRs + music + focus) | 90 seconds | 1 hour |
| Full (all services) | 4.5 minutes | 3 hours |
Intervals grow linearly with idle time. Hooks trigger immediate refreshes on user activity.
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.
- 5d ago First seen · 145 lines · 1,156 tokens per session scan A 1a988d943f9c
fiale-claude-plugins CLAUDE.md is an instructions file published in the GitHub repository fiale-plus/fiale-claude-plugins (4 stars, last pushed 4mo ago), licensed MIT. It adds 1,156 tokens to every session, about $0.0058 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
claude-code-usage-bar AGENTS.md
AGENTS.md instructions for leeguooooo/claude-code-usage-bar, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
netdata AGENTS.md
AGENTS.md instructions for netdata/netdata, covering agents.md, goals, requirement language, working with the user and development principles.
openstatus AGENTS.md
AGENTS.md instructions for openstatusHQ/openstatus, covering agents.md, verify your change, toolchain, architecture and tests.
ai-workflow AGENTS.md
Instructions for cunhaax/ai-workflow, covering ai workflow template, rules — non-negotiable, project overview, commands and architecture.
kubeledger CLAUDE.md
Claude Code instructions for realopslabs/kubeledger, covering claude.md, project overview, development commands, dependency management and install dependencies.
sentry-instrumentation AGENTS.md
Instructions for tortastudios/sentry-instrumentation, covering agents guide — sentry-instrumentation, what this repo is, this repo has no "skill registry", if you're a codex agent asked to install this skill and skill-enable block (copy into consumer agents.md).