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/timeverse/my-tw-coverage/claude-mdgit clone --depth 1 https://github.com/Timeverse/My-TW-CoverageWrote 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/timeverse/my-tw-coverage/claude-md)<a href="https://agentmods.dev/instructions/timeverse/my-tw-coverage/claude-md"><img src="https://agentmods.dev/badge/instructions/timeverse/my-tw-coverage/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.02740 | $0.02740 |
| Opus 5 | $0.01370 | $0.01370 |
| Sonnet 5 | $0.00548 | $0.00548 |
| Haiku 4.5 | $0.00274 | $0.00274 |
Grade A, and why
My-TW-Coverage 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
My TW Coverage — Project Rules
Purpose
Equity research coverage of 1,735+ Taiwan-listed companies (TWSE + OTC). Each ticker report maps business overview, supply chain position, and customer/supplier relationships. Wikilinks [[...]] are the core mechanism — they create a searchable cross-reference graph across all tickers (e.g., find every company serving [[Apple]] or participating in [[矽光子]] supply chain).
Golden Rules
1. Wikilinks Must Be Specific Proper Nouns (MOST IMPORTANT RULE)
Every [[wikilink]] MUST resolve to a specific, searchable proper noun: a company name, product name, named technology, named material, or named process. Generic category words must NEVER be wikilinked.
Three categories of wikilinks — all equally important:
A. Companies: [[台積電]], [[Apple]], [[Bosch]]
B. Named Technologies & Products: [[CoWoS]], [[HBM]], [[矽光子]], [[VCSEL]], [[MLCC]], [[ABF 載板]], [[EUV]]
C. Named Materials & Chemicals: [[光阻液]], [[研磨液]], [[超純水]], [[氦氣]], [[氖氣]], [[鈦酸鋇]], [[聚醯亞胺]]
The purpose: a user searching [[CoWoS]] should find every company involved in CoWoS packaging. Searching [[光阻液]] should find every supplier and consumer of photoresist. If a technology, product, or material is specific enough to be a meaningful search term, it MUST be wikilinked.
Examples of technology/material wikilinks to ALWAYS include when mentioned:
| Category | Must-wikilink examples |
|---|---|
| Packaging | [[CoWoS]], [[InFO]], [[FOPLP]], [[CPO]], [[HBM]], [[2.5D 封裝]], [[3D 封裝]] |
| Photonics | [[矽光子]], [[EML]], [[VCSEL]], [[光收發模組]], [[CPO]] |
| Processes | [[EUV]], [[蝕刻]], [[CVD]], [[PVD]], [[CMP]], [[微影]], [[磊晶]] |
| Materials | [[光阻液]], [[研磨液]], [[超純水]], [[ABF]], [[BT 樹脂]], [[銅箔]], [[玻纖布]] |
| Substrates | [[ABF 載板]], [[BT 載板]], [[矽晶圓]], [[碳化矽]], [[氮化鎵]], [[磷化銦]] |
| Components | [[MLCC]], [[MOSFET]], [[IGBT]], [[導線架]], [[探針卡]] |
| Applications | [[AI 伺服器]], [[電動車]], [[5G]], [[低軌衛星]], [[資料中心]] |
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 · 187 lines · 2,740 tokens per session scan A be63ef0a0b41
My-TW-Coverage CLAUDE.md is an instructions file published in the GitHub repository Timeverse/My-TW-Coverage (546 stars, last pushed 5mo ago), licensed MIT. It adds 2,740 tokens to every session, about $0.0137 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
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.