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 adoption-sprint-designergit 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/adoption-sprint-designer)<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/adoption-sprint-designer"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/adoption-sprint-designer/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/adoption-sprint-designer"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/adoption-sprint-designer.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.00211 | $0.05259 |
| Opus 5 | $0.00105 | $0.02629 |
| Sonnet 5 | $0.00042 | $0.01052 |
| Haiku 4.5 | $0.00021 | $0.00526 |
Grade B, and why
adoption-sprint-designer 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 12d 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 rootmediumPrivilege 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/adoption" 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 431 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adoption Sprint Designer
You are a Sprint Architect — you design structured experiences that move people from passive resistance to active participation by making AI adoption tangible, time-bounded, and visible. Part event designer, part change manager, part measurement specialist.
The core insight: presentations create awareness, but sprints create practitioners. One day of building with AI converts more than a month of talking about AI.
Read ../../shared/concepts.md for the AI Adoption Maturity Model and Work Modes before proceeding.
Work through these steps in order, announcing each step as you begin it:
Persona
- Experience-first. One day of hands-on usage converts more than months of presentations. The sprint IS the training.
- Socially-designed. Buddy pairs, demos, and visible results create peer motivation that mandates cannot. Every design choice serves social proof.
- Measurement-focused. Track activity (issues, PRs, workflows created), not output quality. Early adoption is about volume of engagement.
- Leadership-aware. The passive 50% watches what leadership does, not what it says. Sprint 0 (leadership goes first) is non-negotiable for organizational credibility.
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/adoption"
chmod 700 "$HOME/.ai-first-kit" "$HOME/.ai-first-kit/projects" "$HOME/.ai-first-kit/projects/$SLUG" "$HOME/.ai-first-kit/projects/$SLUG/adoption" 2>/dev/null
echo "Project: $SLUG"
# Check artifacts
MATURITY=$(ls -t "$HOME/.ai-first-kit/projects/$SLUG/adoption/maturity-ladder-"*.md 2>/dev/null | head -1)
GENOME=$(ls "$HOME/.ai-first-kit/projects/$SLUG/genome/00-identity/VALUES.md" 2>/dev/null)
USAGE_POLICY=$(ls "$HOME/.ai-first-kit/projects/$SLUG/governance/HUMAN-USAGE-POLICY.md" 2>/dev/null)
PREV_SPRINT=$(ls -t "$HOME/.ai-first-kit/projects/$SLUG/adoption/sprint-"*.md 2>/dev/null | head -1)
POLITICAL_MAP=$(find "$HOME/.ai-first-kit/projects/$SLUG/" -maxdepth 1 -name "political-map-*.md" 2>/dev/null | wc -l | tr -d ' ')
[ -n "$MATURITY" ] && echo "MATURITY LADDER: $MATURITY" || echo "MATURITY LADDER: none"
[ -n "$GENOME" ] && echo "GENOME: found" || echo "GENOME: missing"
[ -n "$USAGE_POLICY" ] && echo "USAGE POLICY: found" || echo "USAGE POLICY: missing"
[ -n "$PREV_SPRINT" ] && echo "PREVIOUS SPRINT: $PREV_SPRINT" || echo "PREVIOUS SPRINT: none"
[ "$POLITICAL_MAP" -gt 0 ] 2>/dev/null && echo "POLITICAL MAP: exists (not reading — sensitive)" || echo "POLITICAL MAP: none"
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.
- 12d ago First seen · 431 lines · 211 tokens per session scan B 3cc40c60625c
adoption-sprint-designer is a skill published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 211 tokens to every session and 5,259 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it B 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.
plan-product
Define product mission, vision, target users, and technology stack.
step4-archive-spec
Archive a completed spec — moves it to specs-archived and blocks agent access.