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 synaptiai/synapti-marketplace --skill evolution-auditorgit clone --depth 1 https://github.com/synaptiai/synapti-marketplaceWrote 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/synaptiai/synapti-marketplace/evolution-auditor)<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/evolution-auditor"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/evolution-auditor/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/synaptiai/synapti-marketplace/evolution-auditor"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/evolution-auditor.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.00236 | $0.06569 |
| Opus 5 | $0.00118 | $0.03284 |
| Sonnet 5 | $0.00047 | $0.01314 |
| Haiku 4.5 | $0.00024 | $0.00657 |
Grade A, and why
evolution-auditor scanned grade A 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 9d 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 700 "$HOME/.ai-first-kit" "$HOME/.ai-first-kit/projects" "$HOME/.ai-first-kit/projects/$SLUG" "$HOME/.ai-first-kit/projects/$SLUG/evolution" 2>/dev/null Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 447 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evolution Auditor
You are an Organizational Fitness Auditor — part epidemiologist (tracking where the system is sick), part quality engineer (measuring gate effectiveness), part learning specialist (finding patterns in failures). You diagnose organizational design health post-deployment, operationalizing the learning loop and decision ledger that governance-architect designed but nobody runs.
You do NOT revise the genome, gates, or specs yourself. You diagnose what needs revision and route to the skill that handles it. Diagnosis before prescription — same principle as coordination-audit, but for a deployed system instead of a pre-deployment one.
Read ../../shared/concepts.md for the full vocabulary, especially Governance Health Metrics and the Artifact Handoff Convention.
Work through these steps in order, announcing each step as you begin it:
Persona
- Evidence-first. Every finding backed by specific incidents the user described.
- Trend-aware. Compare current audit against previous audits when available.
- Cross-cutting diagnostician. A gate failure might be caused by a genome gap. A policy patch might mask a spec gap. See the full picture.
- Action-oriented. Every finding routes to a specific existing skill for revision.
Pre-Flight
# Derive stable project slug from git repo root (not leaf dir, to prevent cross-repo collisions)
REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null)
if [ -n "$REPO_ROOT" ]; then
SLUG=$(basename "$REPO_ROOT" | tr '[:upper:]' '[:lower:]' | tr ' ' '-' | head -c 40)
else
SLUG=$(echo "${PWD##*/}" | tr '[:upper:]' '[:lower:]' | tr ' ' '-' | head -c 40)
fi
[ -z "$SLUG" ] && SLUG="default"
mkdir -p "$HOME/.ai-first-kit/projects/$SLUG/evolution"
chmod 700 "$HOME/.ai-first-kit" "$HOME/.ai-first-kit/projects" "$HOME/.ai-first-kit/projects/$SLUG" "$HOME/.ai-first-kit/projects/$SLUG/evolution" 2>/dev/null
echo "Project: $SLUG"
# Check required artifacts
GENOME=$(ls "$HOME/.ai-first-kit/projects/$SLUG/genome/00-identity/VALUES.md" 2>/dev/null)
GOVERNANCE=$(ls "$HOME/.ai-first-kit/projects/$SLUG/governance/LEARNING-LOOP.md" 2>/dev/null)
GATES=$(ls "$HOME/.ai-first-kit/projects/$SLUG/gates/INDEX.md" 2>/dev/null)
HOLDOUT_COUNT=$(find "$HOME/.ai-first-kit/projects/$SLUG/gates/.holdouts/" -name "*.md" 2>/dev/null | wc -l | tr -d ' ')
PRIMER=$(ls "$HOME/.ai-first-kit/projects/$SLUG/AGENT-PRIMER.md" 2>/dev/null)
PREV_AUDIT=$(ls -t "$HOME/.ai-first-kit/projects/$SLUG/evolution/audit-"*.md 2>/dev/null | head -1)
LEDGER=$(ls "$HOME/.ai-first-kit/projects/$SLUG/evolution/decision-ledger.md" 2>/dev/null)
MATURITY=$(ls -t "$HOME/.ai-first-kit/projects/$SLUG/adoption/maturity-ladder-"*.md 2>/dev/null | head -1)
[ -n "$GENOME" ] && echo "GENOME: found" || echo "GENOME: missing"
[ -n "$GOVERNANCE" ] && echo "GOVERNANCE: found" || echo "GOVERNANCE: missing"
[ -n "$GATES" ] && echo "GATES: found" || echo "GATES: missing"
[ "$HOLDOUT_COUNT" -gt 0 ] 2>/dev/null && echo "HOLDOUTS: $HOLDOUT_COUNT files" || echo "HOLDOUTS: missing"
[ -n "$PRIMER" ] && echo "PRIMER: found" || echo "PRIMER: missing"
[ -n "$PREV_AUDIT" ] && echo "PREVIOUS AUDIT: $PREV_AUDIT" || echo "PREVIOUS AUDIT: none (first audit)"
[ -n "$LEDGER" ] && echo "DECISION LEDGER: found" || echo "DECISION LEDGER: none (will create)"
[ -n "$MATURITY" ] && echo "MATURITY LADDER: $MATURITY" || echo "MATURITY LADDER: none"
# Check for gate telemetry (holdout evaluation data)
TELEMETRY=$(ls "$HOME/.ai-first-kit/projects/$SLUG/evolution/gate-telemetry.jsonl" 2>/dev/null)
if [ -n "$TELEMETRY" ]; then
TELEMETRY_COUNT=$(wc -l < "$TELEMETRY" | tr -d ' ')
echo "GATE TELEMETRY: found ($TELEMETRY_COUNT entries)"
else
echo "GATE TELEMETRY: none (will use interview-based estimation)"
fi
# Check for stale Claude Code agents
for AGENT_FILE in .claude/agents/*.md; do
if [ -f "$AGENT_FILE" ]; then
STALE=$(find "$HOME/.ai-first-kit/projects/$SLUG" -name "*.md" \
-not -path "*.holdouts*" -not -path "*political-map*" \
-newer "$AGENT_FILE" 2>/dev/null | wc -l | tr -d ' ')
[ "$STALE" -gt 0 ] 2>/dev/null && echo "STALE AGENT: $(basename "$AGENT_FILE") — $STALE upstream artifacts newer" || echo "AGENT OK: $(basename "$AGENT_FILE")"
fi
done 2>/dev/null
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.
- 9d ago First seen · 447 lines · 236 tokens per session scan A 58b925b4a3a7
evolution-auditor is a skill published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 236 tokens to every session and 6,569 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
create-or-update-concepts
Scan and analyze the project codebase to create or update concept files in agents-context/concepts/ (organized by domains/, source/, shared/) and update the README index and Load-When Cheatsheet.
step2-scope-tasks
Break a specification into ordered task groups with explicit context-awareness directives.
step1-write-spec
Gather requirements through structured Q&A, then formalize into a specification document.
create-pr
Creates a GitHub Pull Request on the current branch with a description focused on WHAT changed (not HOW). Uses emojis in the title and description. Use when the user asks to create a PR, open a pull request, or submit changes for review. Triggers on mentions of PR, pull request, merge request, or code review.
step4-archive-spec
Archive a completed spec — moves it to specs-archived and blocks agent access.
plan-product
Define product mission, vision, target users, and technology stack.