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 skills add bookforge-ai/bookforge-skills --skill component-identifiergit clone --depth 1 https://github.com/bookforge-ai/bookforge-skillsWrote 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/skills/bookforge-ai/bookforge-skills/component-identifier)<a href="https://agentmods.dev/skills/bookforge-ai/bookforge-skills/component-identifier"><img src="https://agentmods.dev/badge/skills/bookforge-ai/bookforge-skills/component-identifier/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/bookforge-ai/bookforge-skills/component-identifier"><img src="https://agentmods.dev/badge/skills/bookforge-ai/bookforge-skills/component-identifier.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00074 | $0.03538 |
| Opus 5 | $0.00037 | $0.01769 |
| Sonnet 5 | $0.00015 | $0.00708 |
| Haiku 4.5 | $0.00007 | $0.00354 |
Grade A, and why
component-identifier 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 8d 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.
The source is not reproduced here
Licensed CC-BY-SA-4.0
The repository is licensed CC-BY-SA-4.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 8d ago First seen · 277 lines · 74 tokens per session scan A 2e6f0f78ab11
component-identifier is a skill published in the GitHub repository bookforge-ai/bookforge-skills (35 stars, last pushed 4mo ago), licensed CC-BY-SA-4.0. It adds 74 tokens to every session and 3,538 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
modular-skills
Build composable skill modules with hub-and-spoke loading. Use when token budget is tight.
architecture-paradigm-domain-driven
Models a business in its own language. Use when the domain has real business rules to capture.
plan
Structured technical planning before implementation — architecture and task breakdown.
Component Conventions
Guidance on composing, naming, and sizing components, designing their props, and keeping their state as local as possible.
frontend-architecture
Component architecture, design patterns, state management strategies, module systems, build tools, and scalable application structure.
architecture-design
Use this skill to design system architecture with documented trade-offs and decisions before any implementation begins. Activates when a feature, system, or component requires non-trivial structural decisions about how components interact, what data stores to use, or how to decompose a problem.