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/hect0x7/jmcomic-ai/agents-mdgit clone --depth 1 https://github.com/hect0x7/jmcomic-aiWrote 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/hect0x7/jmcomic-ai/agents-md)<a href="https://agentmods.dev/instructions/hect0x7/jmcomic-ai/agents-md"><img src="https://agentmods.dev/badge/instructions/hect0x7/jmcomic-ai/agents-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.01799 | $0.01799 |
| Opus 5 | $0.00899 | $0.00899 |
| Sonnet 5 | $0.00360 | $0.00360 |
| Haiku 4.5 | $0.00180 | $0.00180 |
Grade A, and why
jmcomic-ai AGENTS.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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Development Guide for JMComic AI
This document provides instructions and best practices for AI Agents (like Antigravity) to develop, maintain, and extend the jmcomic-ai project.
🎯 Core Philosophy
The mission of this project is to transform the JMComic crawler into an AI-native cognitive asset.
- Tools over Scripts: Don't just write scripts; build robust MCP tools that agents can use to reason and act.
- Documentation as Code: Documentation (like
SKILL.md) is the "brain" of the agent. It must be kept in sync with the implementation. - Self-Introspection: The project should expose its own schema and reference through MCP Resources.
🏗️ Architecture for Agents
src/jmcomic_ai/core.py: The "Brain". All business logic and tool implementations reside here inJmcomicService.src/jmcomic_ai/mcp/server.py: The "Interface". UsesFastMCPto dynamically register methods fromJmcomicServiceas MCP tools.src/jmcomic_ai/skills/manager.py: The "Distributor". Owns platform-specific Agent Skills installation paths and safe install/uninstall behavior.reference/jmcomic_src/: The "Knowledge Base". Contains the source code of the underlyingjmcomiclibrary. Always read this first when implementing new tools.
[!IMPORTANT] CRITICAL SOURCE CODE RULE Do NOT attempt to locate the
jmcomicsource code usingpython -c "import jmcomic; print(jmcomic.__file__)"orpip show. The installed version in site-packages is IRRELEVANT for development reference. You MUST strictly use the local copy inreference/jmcomic_src/for all code analysis and logic extraction. Ignoring this rule leads to incorrect path assumptions and wasted steps.
🛠️ Development Workflow (Recommended for Agents)
When asked to add a new feature or tool, follow these steps:
1. Research & Discovery
- STOP & READ: Go directly to
reference/jmcomic_src/. Do not check installed packages. - Search
reference/jmcomic_src/to find the relevant logic in the base library. - For example, if adding a "favorite" feature, search for
favoritein the reference code to see howJmcomicClienthandles it.
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 · 123 lines · 1,799 tokens per session scan A d808bd098bd1
jmcomic-ai AGENTS.md is an instructions file published in the GitHub repository hect0x7/jmcomic-ai (100 stars, last pushed 24d ago), licensed MIT. It adds 1,799 tokens to every session, about $0.0090 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-30.
Other instructions, from other repositories
zscaler-mcp-server CLAUDE.md
Instructions for zscaler/zscaler-mcp-server, covering zscaler mcp server, architecture overview, core components, request flow and service architecture.
zscaler-mcp-server GEMINI.md
Instructions for zscaler/zscaler-mcp-server, covering zscaler mcp server, tool naming & discovery, critical gotchas, write operations — safety rules and zdx filtering.
blockrun-mcp AGENTS.md
AGENTS.md instructions for BlockRunAI/blockrun-mcp, covering blockrun mcp, commands, project structure, key dependencies and install in codex.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
intervals-icu-mcp CLAUDE.md
Claude Code instructions for hhopke/intervals-icu-mcp, covering claude.md, project overview, development commands, architecture (quick reference) and tool categories.
flyto-core CLAUDE.md
Claude Code instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.