duck8823

Traceary — Security skill for Claude Code

Security community

Local-first session log and audit trail for AI coding agents (Claude Code, Codex, Gemini).

How to install Traceary

This entry records only its repository, not the path inside it, so there is no exact command to give. Open duck8823/traceary and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Traceary does

Local-first session log and audit trail for AI coding agents (Claude Code, Codex, Gemini).

Alternatives in Security

Anthropic Cybersecurity Skills — 734+ structured cybersecurity skills for AI agents · MITRE ATT&CK mapped · agentskills.io open standard · Work 3.8k ★
Agent Memory Vault — Markdown-first shared memory vault for Claude Code and Codex with SQLite, Zvec, Git, closeout, and audit 314 ★
Audit Agent Sessions — Analyze all agent sessions from the last 3 days across Claude, Codex, and Gemini 238 ★

README

Traceary

[日本語](./README.ja.md)

Traceary mark

[![CI](https://github.com/duck8823/traceary/actions/workflows/ci.yml/badge.svg)](https://github.com/duck8823/traceary/actions/workflows/ci.yml) [![Release](https://github.com/duck8823/traceary/actions/workflows/release.yml/badge.svg?event=push)](https://github.com/duck8823/traceary/actions/workflows/release.yml)

Traceary is a local-first CLI for recording and searching AI agent work logs, session boundaries, and shell command audits.

Install the CLI first, then add the plugin for your AI agent host to enable automatic recording.

Why Traceary

AI-assisted development gets messy quickly when:

session context disappears after clear or compact
Git history explains what changed, but not always why
shell command output is hard to connect back to the right agent or session
work is split across Claude, Codex, Antigravity (Gemini CLI for legacy installs), and manual terminal steps
multiple sessions and worktree moves make the timeline harder to follow

Traceary keeps those records in one local SQLite store so the same history can be reused from the CLI and hooks.

Three-layer model

Traceary is no longer just a local event log. `v0.5.0` organizes the product around three layers that map to how agent workflows actually need context.

Layer	What lives there	How it is fed
Audit / Archive	raw events (prompts, transcripts, command audits), session boundaries	host hooks (`SessionStart`, `UserPromptSubmit` / `BeforeAgent`, `PostToolUse` / `AfterTool`, `Stop` / `AfterAgent`, `PreCompact` / `PreCompress`, `SessionEnd`) — see host coverage matrix
Working memory	handoff / context packs assembled from recent sessions	handoff packs are assembled on demand by `traceary context --handoff` (raw events remain `traceary context`). From v0.34 the session summary itse