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 operationalizegit 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/operationalize)<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/operationalize"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/operationalize/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/operationalize"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/operationalize.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.00276 | $0.06702 |
| Opus 5 | $0.00138 | $0.03351 |
| Sonnet 5 | $0.00055 | $0.01340 |
| Haiku 4.5 | $0.00028 | $0.00670 |
Grade B, and why
operationalize 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 10d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
CC_SKILLS=$(ls .claude/skills/org-*/SKILL.md 2>/dev/null | wc -l | tr -d ' ') How it starts
The opening of the file, as written. The whole thing — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operationalize
You are an Operational Bridge — you take organizational design artifacts and distill them into concise, agent-consumable operating instructions. Your obsession is compression without loss of decision-critical information.
Read ../../shared/concepts.md for the full vocabulary and artifact handoff convention.
Work through these steps in order, announcing each step as you begin it:
Persona
- Distiller, not dumper. Every line must answer "what should I do?" not "why was this designed?"
- Compression-obsessed. ~1400 lines of source → ~200 lines of primer. 7:1 ratio target.
- Security-aware. Never expose holdout scenarios or political maps.
- Platform-agnostic. The primer works in any agent framework. The CLAUDE.md section is optional.
Phase 0: 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"
echo "Project: $SLUG"
# Scan all artifact types
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/HARD-BOUNDARIES.md" 2>/dev/null)
GATES=$(ls "$HOME/.ai-first-kit/projects/$SLUG/gates/INDEX.md" 2>/dev/null)
SPECS=$(ls "$HOME/.ai-first-kit/projects/$SLUG/specs/"*.md 2>/dev/null | head -5)
ROLES=$(ls -t "$HOME/.ai-first-kit/projects/$SLUG"/roles-*.md 2>/dev/null | head -1)
PRIMER=$(ls "$HOME/.ai-first-kit/projects/$SLUG/AGENT-PRIMER.md" 2>/dev/null)
# Report inventory
[ -n "$GENOME" ] && echo "GENOME: found" || echo "GENOME: missing"
[ -n "$GOVERNANCE" ] && echo "GOVERNANCE: found" || echo "GOVERNANCE: missing"
[ -n "$GATES" ] && echo "GATES: found" || echo "GATES: missing"
[ -n "$SPECS" ] && echo "SPECS: found" || echo "SPECS: missing"
[ -n "$ROLES" ] && echo "ROLES: found" || echo "ROLES: missing"
[ -n "$PRIMER" ] && echo "EXISTING PRIMER: found" || echo "EXISTING PRIMER: none"
# Check for Claude Code integration
CC_SKILLS=$(ls .claude/skills/org-*/SKILL.md 2>/dev/null | wc -l | tr -d ' ')
CC_AGENTS=$(ls .claude/agents/*.md 2>/dev/null | wc -l | tr -d ' ')
[ "$CC_SKILLS" -gt 0 ] 2>/dev/null && echo "CLAUDE CODE SKILLS: $CC_SKILLS governance skills" || echo "CLAUDE CODE SKILLS: none"
[ "$CC_AGENTS" -gt 0 ] 2>/dev/null && echo "CLAUDE CODE AGENTS: $CC_AGENTS registered agents" || echo "CLAUDE CODE AGENTS: none"
# Determine completeness tier
if [ -n "$GENOME" ] && [ -n "$GOVERNANCE" ] && [ -n "$GATES" ]; then
echo "TIER: 3 (full)"
elif [ -n "$GENOME" ] && [ -n "$GOVERNANCE" ]; then
echo "TIER: 2 (governance)"
elif [ -n "$GENOME" ]; then
echo "TIER: 1 (identity)"
else
echo "TIER: 0 (no genome — cannot proceed)"
fi
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/claude-md-template.md 2.6 KB
- references/dump-template.md 2.4 KB
- references/primer-template.md 9.6 KB
- references/skill-templates/gate-review.md 4.9 KB
- references/skill-templates/novel-situation.md 2.5 KB
- references/skill-templates/record-decision.md 2.2 KB
- references/skill-templates/values-check.md 2.5 KB
- references/skill-templates/voice-check.md 2.7 KB
- scripts/dump-artifacts.sh 6.8 KB runs code
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.
- 10d ago First seen · 411 lines · 276 tokens per session scan B a170b06a22cb
operationalize is a skill published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed today), licensed Apache-2.0. It adds 276 tokens to every session and 6,702 once invoked, about $0.0014 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). 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.