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 skills add terrylica/cc-skills --skill session-chroniclegit clone --depth 1 https://github.com/terrylica/cc-skillsWrote 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/terrylica/cc-skills/session-chronicle)<a href="https://agentmods.dev/skills/terrylica/cc-skills/session-chronicle"><img src="https://agentmods.dev/badge/skills/terrylica/cc-skills/session-chronicle/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.
<a href="https://agentmods.dev/skills/terrylica/cc-skills/session-chronicle"><img src="https://agentmods.dev/badge/skills/terrylica/cc-skills/session-chronicle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 61 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- high Rogue Agent · line 402 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00027 | $0.03775 |
| Opus 5 | $0.00014 | $0.01887 |
| Sonnet 5 | $0.00005 | $0.00755 |
| Haiku 4.5 | $0.00003 | $0.00378 |
Grade B, and why
session-chronicle scanned grade B with 1 finding 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
SKILL_DIR="$(find $HOME/.claude/plugins/marketplaces/cc-skills -type d -name session-chronicle | head -1)" How it starts
The opening of the file, as written. The whole thing — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Chronicle
Excavate Claude Code session logs to capture complete provenance for research findings, ADR decisions, and code contributions. Traces UUID chains across multiple auto-compacted sessions.
CRITICAL PRINCIPLE: Registry entries must be self-contained. Record ALL session UUIDs (main + subagent) at commit time. Future maintainers should not need to run archaeology to understand provenance.
S3 Artifact Sharing: Artifacts can be uploaded to S3 for team access. See S3 Sharing ADR.
Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.
When to Use This Skill
- User asks "who created this?" or "where did this come from?"
- User says "document this finding" with full session context
- ADR or research finding needs provenance tracking
- Git commit needs session UUID references
- Tracing edits across auto-compacted sessions
- Creating a registry entry for a research session
File Ownership Model
| Directory | Committed? | Purpose |
|---|---|---|
findings/registry.jsonl |
YES | Master index (small, append-only NDJSON) |
findings/sessions/<id>/iterations.jsonl |
YES | Iteration records (small, append-only) |
outputs/research_sessions/<id>/ |
NO | Research artifacts (large, gitignored) |
tmp/ |
NO | Temporary archives before S3 upload |
S3 eonlabs-findings/sessions/<id>/ |
N/A | Permanent team-shared archive |
Key Principle: Only findings/ is committed. Research artifacts go to gitignored outputs/ and S3.
What ships with it
31 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.
- references/archaeology-scripts.md 4.2 KB
- references/evolution-log.md 683 B
- references/output-generation.md 2.6 KB
- references/preflight-scripts.md 3.7 KB
- references/provenance-schema.json 5.2 KB
- references/registry-schema.md 4.1 KB
- references/s3-manifest-schema.json 5.9 KB
- references/s3-retrieval-guide.md 4.5 KB
- references/session-entry-schema.json 3.4 KB
- scripts/extract_context.sh 1.4 KB runs code
- scripts/extract_session_chain.sh 4.2 KB runs code
- scripts/generate_commit_message.sh 2.9 KB runs code
- scripts/retrieve_artifact.sh 4.6 KB runs code
- scripts/s3_upload.sh 4.2 KB runs code
- scripts/sanitize_sessions.py 16 KB runs code
- scripts/search_sessions.sh 1.8 KB runs code
- scripts/session_indexer.sh 2.1 KB runs code
- scripts/uuid_tracer.sh 3.8 KB runs code
- tests/AUDIT-REPORT-2026-01-02.md 7.7 KB
- tests/fixtures/expected-manifest.json 342 B
- tests/fixtures/mock-session.jsonl 848 B
- tests/fixtures/mock-uuid-chain.jsonl 490 B
- tests/README.md 2.5 KB
- tests/scripts/validate-brotli.sh 1.9 KB runs code
- tests/scripts/validate-commit-format.sh 2.2 KB runs code
- tests/scripts/validate-credential-access.sh 1.9 KB runs code
- tests/scripts/validate-cross-references.sh 4.1 KB runs code
- tests/scripts/validate-e2e.sh 1.1 KB runs code
- tests/scripts/validate-extract-chain.sh 1.7 KB runs code
- tests/scripts/validate-prerequisites.sh 940 B runs code
- tests/scripts/validate-s3-upload.sh 3.9 KB runs code
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.
- 3d ago First seen · 405 lines · 27 tokens per session scan B d404f5836469
session-chronicle is a skill published in the GitHub repository terrylica/cc-skills (62 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 3,775 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, testing, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, testing strategy, and communication standards.
ship
Commit, push, create PR(s), and auto-finalize — full automation pipeline. Handles uncommitted changes and recently created PRs.
git-flow-next
Work with repositories using the git-flow-next branching model (default branch is develop, production branch is main). Covers branch creation, worktree setup, atomic commits, PR targeting, validation on develop, and mandatory end-of-session promotion to main.
troubleshoot-precommit
Troubleshoot pre-commit hook failures and auto-fixes.
git-workflow
Skill "git-workflow" from halflength-ampleness75/claude-code-recipes, covering git workflow, branch naming, rules, conventional commits and format.
workspace-standards
Use when setting up or managing multi-repo workspaces.