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 agentmods add commands/kynto-consulting/capsule/buildgit clone --depth 1 https://github.com/Kynto-Consulting/capsuleWrote 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/commands/kynto-consulting/capsule/build)<a href="https://agentmods.dev/commands/kynto-consulting/capsule/build"><img src="https://agentmods.dev/badge/commands/kynto-consulting/capsule/build.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00784 |
| Opus 5 | $0.00000 | $0.00392 |
| Sonnet 5 | $0.00000 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
build 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Commands — Capsule
Overview
This document describes how to build each component of the Capsule project.
Prerequisites
| Tool | Minimum Version | Purpose |
|---|---|---|
| Go | 1.22+ | Backend & CLI |
| Node.js | 20+ | Frontend (Next.js) |
| pnpm | 9+ | Frontend pkg manager |
| Docker | 24+ | Container builds |
| Make | 3.81+ | Build orchestration |
Build All Components
make build
This runs the backend, frontend, and CLI builds sequentially.
Backend (Go API Server)
# From project root
cd backend
go build -o ../bin/capsule-server ./cmd/server
# With version info embedded
go build -ldflags "-X main.version=$(git describe --tags --always) -X main.commit=$(git rev-parse --short HEAD) -X main.buildDate=$(date -u +%Y-%m-%dT%H:%M:%SZ)" \
-o ../bin/capsule-server ./cmd/server
Build flags
| Flag | Description |
|---|---|
-race |
Enable race detector (dev only) |
-trimpath |
Remove file system paths from binary |
-ldflags "-s -w" |
Strip debug info for smaller binary |
Frontend (Next.js Dashboard)
# From project root
cd frontend
# Install dependencies
pnpm install
# Development build
pnpm dev
# Production build
pnpm build
# Export static assets (if applicable)
pnpm export
Environment Variables
Create frontend/.env.local for local development:
NEXT_PUBLIC_API_URL=http://localhost:8080
NEXT_PUBLIC_WS_URL=ws://localhost:8080
CLI (capsule-cli)
# From project root
cd cli
go build -o ../bin/capsule ./cmd/capsule
# Cross-compile for Linux
GOOS=linux GOARCH=amd64 go build -o ../bin/capsule-linux-amd64 ./cmd/capsule
# Cross-compile for macOS (Apple Silicon)
GOOS=darwin GOARCH=arm64 go build -o ../bin/capsule-darwin-arm64 ./cmd/capsule
# Cross-compile for Windows
GOOS=windows GOARCH=amd64 go build -o ../bin/capsule-windows-amd64.exe ./cmd/capsule
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.
- 3d ago First seen · 138 lines · 0 tokens per session scan A 3220c80e890b
build is a command published in the GitHub repository Kynto-Consulting/capsule (2 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 784 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.