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/shimo4228/claude-harness/jsonld-knowledge-graphnpx skills add shimo4228/claude-harness --skill jsonld-knowledge-graphgit clone --depth 1 https://github.com/shimo4228/claude-harnessWrote 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/shimo4228/claude-harness/jsonld-knowledge-graph)<a href="https://agentmods.dev/skills/shimo4228/claude-harness/jsonld-knowledge-graph"><img src="https://agentmods.dev/badge/skills/shimo4228/claude-harness/jsonld-knowledge-graph.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.00090 | $0.07011 |
| Opus 5 | $0.00045 | $0.03506 |
| Sonnet 5 | $0.00018 | $0.01402 |
| Haiku 4.5 | $0.00009 | $0.00701 |
Grade A, and why
jsonld-knowledge-graph 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.
This is a copy
100% identical to jsonld-knowledge-graph — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JSON-LD Knowledge Graph
graph.jsonld を llms.txt の隣に置いて、project の concept-level architecture を schema.org JSON-LD triples として encode する skill。LLM が prose だけでは引き出しにくい entity 間の関係（matrix / hierarchy / phase-binding）を triple として citation 可能にする。
When to Use
以下を すべて 満たす project に適用する:
- 安定した concept-level 構造を持つ
- 例: matrix（4 Quadrants × N ADRs）、ordered hierarchy（prohibition-strength 3 levels）、phase-skill binding（6:6 bijective）、layered architecture（3 memory layers）
- 構造が release を跨いで安定（vX.Y.Z bump で entity が増減しない）
- LLM に当該関係を訊いた時に prose だけでは答が出にくい / 誤答する 経験的証拠がある
- すでに
llms.txt+llms-full.txt（Answer.AI 標準）を持っている
When NOT to Use
以下のいずれかに該当する場合は 適用しない:
- 単一目的の linear project（matrix / hierarchy 構造がない）
- 内部構造が release ごとに churn する（graph が編集負債になる）
llms-full.txtの prose Q&A で関係問題が既に十分答えられる- 「LLM citation 向上を狙いたい」だけで具体的な entity 関係問題がない（GEO 目的なら llms-txt-writer の方が direct）
graph.jsonld は prose の代替ではなく 補完。prose で表現しきれない構造があるとき、その構造をやっと拾える。
CODEMAPS との関係（正本）
graph.jsonld と CODEMAPS（典型的には docs/CODEMAPS/architecture.md）は 同じ project を異なる abstraction 層で扱う:
| CODEMAPS | graph.jsonld | |
|---|---|---|
| 対象 | ファイル / モジュール | 概念 / エンティティ |
| 抽象層 | file-level | concept-level |
| 答える質問 | 「X はどのファイルに住んでいるか」 | 「X とは何か、X と Y はどう関係するか」 |
| 形式 | prose（Markdown） | JSON-LD triples |
| 主読者 | 人間 + agent が code を navigate する時 | AI search engine + LLM が entity を citation する時 |
| trigger | code 構造の変化 | concept / 関係の変化 |
両者は 重複せず相補的。同じ entity を別角度から見る。例えば AAP の Quadrant ノード:
- CODEMAPS は「Quadrants の解説は
docs/quadrants/README.mdに住む、governance-mapping.mdが matrix 表」と書く（file-level） - graph.jsonld は「Quadrant 3 (LLM Workflow) に ADR-0001/0003-0007 が
appliesTo、governanceTier: medium、xAxis: semantic-judgment」と書く（concept-level）
Drift 防止のための運用規約
新規 entity を追加する時は 両面で更新する:
- 新規 ADR / Concept / Quadrant 等を追加 → graph.jsonld にノード追加 + CODEMAPS の該当 file path 言及を更新
- ファイルパスが変わった → CODEMAPS 更新（graph.jsonld の
@idは GitHub blob URL を使っているなら追従が必要） - 概念の semantics が変わった → graph.jsonld の description 更新（CODEMAPS は触らなくてよい）
What ships with it
2 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 · 393 lines · 90 tokens per session scan A a95604e01a49
jsonld-knowledge-graph is a skill published in the GitHub repository shimo4228/claude-harness (2 stars, last pushed 6d ago), licensed MIT. It adds 90 tokens to every session and 7,011 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to jsonld-knowledge-graph, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
zod
Zod v4 best practices, patterns, and API guidance for schema validation, parsing, error handling, and type inference in TypeScript applications. Covers safeParse, object composition, refinements, transforms, codecs, branded types, v3→v4 migration, and testing schemas with Jest or Vitest. Baseline: zod ^4.3.0. Triggers…
jest
Jest best practices, patterns, and API guidance for JavaScript/TypeScript testing. Covers mock design, async testing, matchers, timer mocks, snapshots, module mocking, configuration, and CI optimization. Baseline: jest ^30.0.0. Triggers on: jest imports, describe, it, test, expect, jest.fn, jest.mock, jest.spyOn…
agent-adoption-triage
Five-question triage for routing AI work to the right architecture — script, algorithmic search, LLM workflow, or autonomous agentic loop — before any agent is built. Use when someone says "let's build an agent for X", when deciding whether a use case actually needs an autonomous agent, when reviewing an agent…
zod-testing
Testing patterns for Zod schemas using Jest and Vitest. Covers schema correctness testing, mock data generation, error assertion patterns, integration testing with API handlers and forms, snapshot testing with z.toJSONSchema(), and property-based testing. Baseline: zod ^4.0.0. Triggers on: test files for Zod schemas…
redux-saga
Redux-Saga best practices, patterns, and API guidance for building, testing, and debugging generator-based side-effect middleware in Redux applications. Covers effect creators, fork model, channels, testing with redux-saga-test-plan, concurrency, cancellation, and modern Redux Toolkit integration. Baseline: redux-saga…
redux-saga-testing
Write tests for Redux Sagas using redux-saga-test-plan, runSaga, and manual generator testing. Covers expectSaga (integration), testSaga (unit), providers, partial matchers, reducer integration, error simulation, and cancellation testing. Works with Jest and Vitest. Triggers on: test files for sagas…