What is jd-jdex-audit?

A folder-structure checker for a Johnny.Decimal system, where numbered folders organize files by area and category. It compares the system’s index (JDex) with folders on disk.

Use it to audit one or more Johnny.Decimal systems, review folder inconsistencies, and identify entries or folders that need correction.

It finds missing folders, unexpected folders, numbering mismatches, and folders not recorded in the index. This helps keep the index and actual files aligned.

jd-jdex-audit — Skill for Claude Code by ngerakines

Install

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.

Any agent

npx skills add ngerakines/jd --skill jd-jdex-audit

Clone the repo

git clone --depth 1 https://github.com/ngerakines/jd

Made for: Claude Code.

Or install jd, the plugin that ships this one along with the rest of its 6 skills, 6 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ngerakines/jd/jd-jdex-audit/github.svg)](https://agentmods.dev/skills/ngerakines/jd/jd-jdex-audit)

Your own site

<a href="https://agentmods.dev/skills/ngerakines/jd/jd-jdex-audit"><img src="https://agentmods.dev/badge/skills/ngerakines/jd/jd-jdex-audit/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ngerakines/jd/jd-jdex-audit"><img src="https://agentmods.dev/badge/skills/ngerakines/jd/jd-jdex-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 103 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,347 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00103	$0.01347
Opus 5	$0.00051	$0.00674
Sonnet 5	$0.00021	$0.00269
Haiku 4.5	$0.00010	$0.00135

Measured 11d ago against content hash 8df3bab64ba1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

jd-jdex-audit 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 11d 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.

jd/skills/jd-jdex-audit/SKILL.md · 204 lines

How it starts

The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Johnny.Decimal JDex Audit

This skill compares a system's JDex (the authoritative index) against the actual folder structure on disk, identifying mismatches and suggesting fixes.

1. Locate the System

1.1 Find the JD Root

Check common locations:

~/Library/Mobile Documents/com~apple~CloudDocs/JD/ (iCloud Drive)
~/Documents/JD/
~/JD/

If the user specifies a system code (e.g., "audit my P10 system"), target that specific system. Otherwise, list all available systems and ask which to audit.

1.2 Load the JDex

Read the JDex file at:

SYS/00-09 */00 */00.00 *JDex*

Parse it into a structured list of areas, categories, and IDs. Each entry should capture:

The AC.ID (or SYS.AC.ID) address
The description/name
Any +SUB entries

1.3 Snapshot the Filesystem

List all folders to depth 3 under the system root. Parse folder names to extract AC.ID addresses, area ranges, and category numbers.

2. Compare JDex vs. Filesystem

Run three checks:

2.1 Orphaned JDex Entries

JDex entries that have no corresponding folder on disk.

These indicate either:

A folder was deleted without updating the JDex
A planned ID that was never created
A typo in the JDex entry

2.2 Undocumented Folders

Folders on disk that have no corresponding JDex entry.

These indicate either:

A folder was created without updating the JDex
The JDex fell out of sync during manual organization
A folder created by another tool or process

2.3 Name Mismatches

JDex entries whose description doesn't match the folder name, or folders whose name doesn't follow the expected AC.ID Description format.

3. Check +SUB Indexes

For categories that use +SUB extensions:

3.1 Locate Index Files

+SUB categories typically have an index file (e.g., 51.01 Open-source project index.md). Find these by looking for files matching *.md at the category or ID level that contain +SUB listings.

3.2 Compare Index vs. Folders

List all +NNNN or +CODE folders within the ID
Compare against the index file entries
Flag missing or extra entries

Read the full file on GitHub · 204 lines

Changes

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.

11d ago First seen · 204 lines · 103 tokens per session scan A 8df3bab64ba1

Subscribe to this mod's changes

jd-jdex-audit is a skill published in the GitHub repository ngerakines/jd (7 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 103 tokens to every session and 1,347 once invoked, about $0.0005 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.

Productivity

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

pinchtab-mcp

Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.

pinchtab/pinchtab · 52 tokens

jd-jdex-audit