Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation-only usage logging skill that stores local audit/session metadata and shows no hidden execution, exfiltration, or destructive behavior.
Install only if you want persistent local usage and audit logs. Avoid placing secrets or sensitive personal data in log metadata, periodically review or delete files under ~/.claude/leyline/usage, and use shared session IDs only when cross-service activity correlation is appropriate.
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.
# View recent logs
tail -20 ~/.claude/leyline/usage/my-service.jsonl | jq .
# Query by date
grep "2025-12-05" ~/.claude/leyline/usage/my-service.jsonl
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.
tail -20 ~/.claude/leyline/usage/my-service.jsonl | jq .
grep "2025-12-05" ~/.claude/leyline/usage/my-service.jsonl
**Verification:** Run the command with `--help` flag to verify availability.
The trigger list includes broad generic terms like 'logging', 'usage', 'audit', 'metrics', 'sessions', and 'analytics', which can cause the skill to activate in many unrelated contexts. Over-broad activation increases the chance of unintended invocation of storage-related behavior and can expose users to logging features they did not explicitly request.
The activation phrase 'or cost tracking to a skill' is grammatically incomplete and ambiguous, making invocation behavior unpredictable. Ambiguous routing cues can cause accidental skill selection in contexts where the user did not intend to enable persistent logging or audit-trail functionality.
The skill describes audit trails and usage logging but does not clearly warn users that data is persisted locally under the agent configuration directory. Because logs may contain operational metadata, session identifiers, timestamps, token counts, and potentially sensitive metadata fields, failing to disclose persistence undermines informed consent and safe handling expectations.
This markdown file includes code that creates and updates a local session.json file containing session identifiers and activity timestamps. While the code comments describe the mechanics, the surrounding documentation does not warn users that usage/session metadata will be persisted locally, which is relevant to privacy and data handling.
The document recommends passing a shared session_id between services and correlating operations across them, which can increase traceability of user activity across systems. The markdown does not disclose this cross-service linkage or its privacy implications to users.