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/scriptxeno/scriptxeno.github.io/claude-mdgit clone --depth 1 https://github.com/ScriptXeno/ScriptXeno.github.ioWhat 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.01401 | $0.01401 |
| Opus 5 | $0.00700 | $0.00700 |
| Sonnet 5 | $0.00280 | $0.00280 |
| Haiku 4.5 | $0.00140 | $0.00140 |
Grade A, and why
ScriptXeno.github.io 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 yesterday.
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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project overview
ScriptXeno is a Jekyll static blog (theme: jekyll-theme-chirpy) deployed to GitHub Pages at
https://scriptxeno.github.io. Content is authored as Markdown posts in _posts/; there is no
backend, database, or JS framework — Jekyll renders everything to _site/ at build time.
Commands
- Install dependencies:
bundle install - Serve locally with live reload:
bash tools/run.sh(wrapsbundle exec jekyll s -l -H 127.0.0.1)-H, --host <host>to change bind address,-p, --productionto run withJEKYLL_ENV=production
- Build + test like CI:
bash tools/test.sh- Cleans
_site, builds withJEKYLL_ENV=production, then runsbundle exec htmlproofer _site --disable-external --ignore-urls ...to check internal links/HTML - Accepts
-c, --config "<file_a[,file_b]>"to build against alternate/multiple config files
- Cleans
- There is no JS package.json / npm pipeline in this repo.
.github/workflows/ci.ymlrunsnpm i && npm run buildbeforetools/test.sh, but nopackage.jsonexists here — that step is leftover from the Chirpy "Starter" template and will fail if the workflow actually runs. Don't assume an npm/rollup build is part of this project;_javascript/and theassets/js/distgitignore entry are similarly vestigial. - No unit test suite exists;
htmlproofer(viatools/test.sh) is the only automated check, and it operates on the built HTML output, not source files.
Architecture
- Theme is fully vendored, not just gem-referenced.
Gemfilepulls injekyll-theme-chirpyas a gem, but_layouts/,_includes/, and_sass/here contain a full local copy of the theme's templates/partials/styles (not the usual handful of override files). Treat these directories as the actual source of truth for markup/styling — the gem mainly supplies Ruby-side behavior (SEO tag, archives, etc.) for anything not locally overridden. - Two local Jekyll plugins in
_plugins/beyond the theme gem:posts-lastmod-hook.rb— setspost.data['last_modified_at']fromgit loghistory for each post.watcher-patch.rb— extendsjekyll-watch's ignored paths (adds*.TMP).
assets/libis a git submodule (chirpy-static-assets), butassets.self_host.enabledis empty/off in_config.yml, so it isn't actually used for asset hosting unless that's turned on.- Deploy/CI workflows in
.github/workflows/:pages-deploy.yml— builds with Ruby 3.3 and deploys to GitHub Pages on push tomain/master.ci.yml— separate PR-time matrix build (Ruby 3.1–3.3) that also runstools/test.sh(see the broken npm step noted above).publish.yml— reacts to pushes on adocsbranch and dispatches adeployevent to another repo viasecrets.BUILDER; this is a vestige of the upstream Chirpy theme template, unrelated to how this blog's own posts get published.
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.
- yesterday First seen · 77 lines · 1,401 tokens per session scan A bb13e6653977
ScriptXeno.github.io CLAUDE.md is an instructions file published in the GitHub repository ScriptXeno/ScriptXeno.github.io (5 stars, last pushed 13d ago), licensed MIT. It adds 1,401 tokens to every session, about $0.0070 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 instructions, from other repositories
jdocmunch-mcp CLAUDE.md
Claude Code instructions for jgravelle/jdocmunch-mcp, covering jdocmunch-mcp, standing operational notes (jdoc-specific), standing lessons (suite-wide), release: the two steps that are only written down here and 1. read ci for the pushed sha before any irreversible step.
docs AGENTS.md
Instructions for argos-ci/docs, covering agents.md, always use the documentation skills and keep the table of contents in sync.
docs-mcp CLAUDE.md
Claude Code instructions for base-kit/docs-mcp, covering docs-mcp 工具开发规范, 项目定位与架构, 开发规范, 索引构建与维护 and 重 build 索引.
libragen AGENTS.md
Instructions for libragen/libragen, covering agent guidelines for libragen, repository structure, package dependencies, key architectural concepts and library manager (packages/core/src/manager.ts).
coven-docs copilot-instructions.md
Copilot instructions for OpenCoven/coven-docs, covering coven-docs, setup and structure.
scribekit CLAUDE.md
Claude Code instructions for daanvandenbergh/scribekit, covering project: scribekit, directory architecture, web testing, demo dev server and git.