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 eveld/claude --skill gather-project-metadatagit clone --depth 1 https://github.com/eveld/claudeWrote 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/eveld/claude/gather-project-metadata)<a href="https://agentmods.dev/skills/eveld/claude/gather-project-metadata"><img src="https://agentmods.dev/badge/skills/eveld/claude/gather-project-metadata/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/eveld/claude/gather-project-metadata"><img src="https://agentmods.dev/badge/skills/eveld/claude/gather-project-metadata.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00023 | $0.00400 |
| Opus 5 | $0.00012 | $0.00200 |
| Sonnet 5 | $0.00005 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
gather-project-metadata 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 8d 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.
What it actually says
Gather Project Metadata
Collect metadata for documentation frontmatter.
What to Gather
- Current timestamp (ISO format with timezone)
- Git commit hash
- Git branch name
- Repository name
- Project name (from directory or package.json)
- Feature slug (if in feature directory context)
How to Gather
Run the metadata collection script:
~/.claude/scripts/collect-metadata.sh
Or gather manually:
# Timestamp
date -u +"%Y-%m-%dT%H:%M:%SZ"
# Git info
git rev-parse HEAD
git rev-parse --abbrev-ref HEAD
git remote get-url origin | sed 's/.*[:/]\(.*\)\.git/\1/'
# Project name
basename $(pwd)
# Feature slug (if applicable)
FEATURE_DIR=$(pwd | grep -oE 'thoughts/[0-9]{4}-[^/]+' || echo "")
if [ -n "$FEATURE_DIR" ]; then
basename "$FEATURE_DIR"
fi
Usage in Documents
Insert gathered metadata into frontmatter:
---
date: 2025-12-23T10:30:00Z
git_commit: abc123...
branch: main
repository: github.com/eveld/claude
---
Template Variables
When using templates, replace these placeholders:
{ISO_TIMESTAMP}- ISO 8601 timestamp{GIT_COMMIT}- Full commit hash{BRANCH_NAME}- Current branch{REPOSITORY}- Repository path{PROJECT_NAME}- Project name{DATE}- Simple date (YYYY-MM-DD){FEATURE_SLUG}- Feature slug (e.g., "0005-authentication")
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.
- 8d ago First seen · 71 lines · 23 tokens per session scan A 61324f5f093c
gather-project-metadata is a skill published in the GitHub repository eveld/claude (10 stars, last pushed 7mo ago), licensed MIT. It adds 23 tokens to every session and 400 once invoked, about $0.0001 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 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.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
auto-claude
Autonomous multi-agent coding with git worktree isolation, QA validation, and memory. Use for complex features requiring autonomous implementation.
research-archival
Scrape AI research URLs, archive with frontmatter, create GitHub Issues with identity verification.
issues-workflow
Plan and track work using a GitHub Issues-first workflow with sub-issue hierarchies, issue-branch-PR lifecycle, and auto-close on merge.
worktree-manager
Create alpha-forge git worktrees with auto branch naming. TRIGGERS - create worktree, new worktree, alpha-forge worktree.