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 skills/alessiomarcone/agent-fieldbook/pluginnpx skills add alessiomarcone/agent-fieldbook --skill plugingit clone --depth 1 https://github.com/alessiomarcone/agent-fieldbookWrote 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/alessiomarcone/agent-fieldbook/plugin)<a href="https://agentmods.dev/skills/alessiomarcone/agent-fieldbook/plugin"><img src="https://agentmods.dev/badge/skills/alessiomarcone/agent-fieldbook/plugin.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.00063 | $0.00450 |
| Opus 5 | $0.00032 | $0.00225 |
| Sonnet 5 | $0.00013 | $0.00090 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
plugin 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.
What it actually says
Plugin
Resolve the product and distribution surface before writing any manifest.
References
Read only the selected product branch:
- Claude Code:
references/claude-code-plugins.md. - Claude Cowork:
references/plugin-building.md. - Codex:
references/codex-plugins.md.
Procedure
- Identify target product, installation model, namespace, and public or private distribution path.
- Inventory only required capabilities: skills, agents/subagents, hooks, MCP/connectors/apps, or supported assets.
- Prefer several focused skills with explicit handoffs over one broad workflow.
- Keep every declared component inside the distributable boundary.
- Use only fields supported by the selected product's current schema.
- Document install, direct invocation, permissions, provenance, update, and uninstall behavior.
- Validate source and packaged artifact; install in a clean environment; test direct and contextual activation.
- For public submission, prepare the exact listing, legal, safety, and reviewer materials required by that ecosystem.
Output contract
Return:
- Target — product, installation model, namespace, and distribution path.
- Architecture — component tree and reason for each component.
- Files — ready-to-use manifests and components when implementation is requested.
- Install and invoke — exact current commands.
- Release gate — validation, clean install, permissions audit, tests, and versioning.
Boundaries
- Do not mix fields from different plugin ecosystems.
- Do not activate for creation or revision of a single standalone skill; route that work to
skill. - Do not declare components without their companion files.
- Do not claim commands, UI paths, or submission requirements without current official support.
- Do not distribute credentials, private data, raw transcripts, or unlicensed material.
- Answer in the user's language.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 47 lines · 63 tokens per session scan A 92e78e995f75
plugin is a skill published in the GitHub repository alessiomarcone/agent-fieldbook (5 stars, last pushed 17d ago), licensed MIT. It adds 63 tokens to every session and 450 once invoked, about $0.0003 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 skills, from other repositories
acontext-installer
Install Acontext, Login & Init Acontext Project, Add Skill Memory to Agent.
lore
Use when answering any domain or knowledge question in a project linked to a lore (its CLAUDE.md has a "## Knowledge Base" section naming the lore path), and as the shared contract for all lore- skills. Defines the lore folder layout, page schema, retrieval ladder, index regeneration, and citation rules.
lore-lint
Use when the user runs /lore:lore-lint — health-check the lore for index drift, ungrouped pages, group hygiene, dead wikilinks, duplicate titles, unresolved contradictions, schema violations, missing footnote attribution, missing concept pages and cross-references, knowledge gaps, and discard candidates. Fix…
lore-init
Use when the user runs /lore:lore-init [path] [--no-git] — create the lore folder, scaffold its layout with its CLAUDE.md schema, and git-init it unless --no-git. Writes nothing outside the lore folder.
lore-ingest
Use when the user runs /lore:lore-ingest — find files in the lore's raw/ inbox that are new or changed since their last ledger entry, distill or surgically update wiki pages by content type, update log.md, regenerate the index, and commit.
forge-writing
文献锚定型学术写作（IMRD 完整四段），三阶深挖 → 创新锚定 → 叙事线走通 → 逐段交互起草 → 综合审校。支持单章写作、全文编排、润色模式。当用户需要写论文段落、起草 Introduction/Discussion/Methods/Results/Abstract/Conclusion、润色已有草稿、讨论论文大纲或写作思路时触发——即使用户没有明确说"写作"，只要涉及论文内容产出（"帮我写一段引言""这个讨论怎么写""润色一下这段""帮我看看这个大纲"）都应使用此 skill。材料科学领域优化，深度整合 SciCrucible 知识库文献。.