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 skills/crypdick/pynchy/pynchy-opsnpx skills add crypdick/pynchy --skill pynchy-opsgit clone --depth 1 https://github.com/crypdick/pynchyWrote 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/crypdick/pynchy/pynchy-ops)<a href="https://agentmods.dev/skills/crypdick/pynchy/pynchy-ops"><img src="https://agentmods.dev/badge/skills/crypdick/pynchy/pynchy-ops.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.00110 | $0.04574 |
| Opus 5 | $0.00055 | $0.02287 |
| Sonnet 5 | $0.00022 | $0.00915 |
| Haiku 4.5 | $0.00011 | $0.00457 |
Grade B, and why
Pynchy Ops 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 4d 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.
ssh "$PYNCHY_HOST" 'sudo k3s kubectl get namespace pynchy' How it starts
The opening of the file, as written. The whole thing — 399 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pynchy Ops
The live Pynchy host and checkout path are deployment-specific. Public repo instructions must not assume a private hostname or home-directory layout. Set PYNCHY_HOST and PYNCHY_REMOTE_ROOT from local memory, environment, or the operator before running remote commands.
Deployment Mode Gate
Identify the live deployment before running an operational command. A pynchy
Kubernetes namespace means the Kubernetes path applies:
PYNCHY_HOST="${PYNCHY_HOST:?set the live host}"
ssh "$PYNCHY_HOST" 'sudo k3s kubectl get namespace pynchy'
For Kubernetes deployments:
- Read Kubernetes installation and operations.
- Treat
SCHEDULER__AUTO_DEPLOY=falseas authoritative. A Git pull updates the persistent checkout but does not replace the running image. - Use
sudo k3s kubectl -n pynchy; do not usepynchy deploy, LaunchAgent commands, standalone systemd commands, or direct container deletion. - A successful push to
mainpublishes immutable images. The namespace-scopedpynchy-release-monitorCronJob preflights and releases them. - Do not manually patch the Deployment or delete a Pod for a normal release. Observe the monitor Job, rollout, exact release annotation, and application status.
- Apply Kubernetes manifest, storage, Secret, RBAC, Pocket TTS, and private MCP image changes manually after review; the application release monitor does not apply infrastructure.
- Keep unrelated Docker Compose and Dockge services outside Kubernetes.
The standalone sections below apply only when the live host has no Kubernetes Pynchy Deployment.
Standalone Auto-deploy: Never Restart Manually
Pynchy self-manages. Two mechanisms trigger automatic restarts:
- Git changes on
main— the polling mechanism detects new commits, pulls, and restarts (with container rebuild if source files changed). - Config file changes — editing
config.toml,litellm_config.yaml, or other settings files triggers an automatic deploy on the next host git-sync poll. The default interval is 300 seconds; check[scheduler].git_sync_interval_secondsbefore deciding it was missed.
What ships with it
3 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.
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.
- 4d ago First seen · 399 lines · 110 tokens per session scan B f85d6e7a2e3c
Pynchy Ops is a skill published in the GitHub repository crypdick/pynchy (10 stars, last pushed 2d ago), licensed MIT. It adds 110 tokens to every session and 4,574 once invoked, about $0.0006 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
add-vercel
Add Vercel deployment capability to NanoClaw agents. Installs the Vercel CLI in agent containers and sets up OneCLI credential injection for api.vercel.com. Use when the user wants agents to deploy web applications to Vercel.
vercel-cli
Deploy apps to Vercel. Use when asked to deploy, ship, or publish a web application, or manage Vercel projects, domains, and environment variables.
manage-mounts
Configure which host directories agent containers can access. View, add, or remove mount allowlist entries. Triggers on "mounts", "mount allowlist", "agent access to directories", "container mounts".
architecture-diagram
Generate dark-themed SVG diagrams of software systems and cloud infrastructure as standalone HTML files with inline SVG graphics. Semantic component colors (cyan=frontend, emerald=backend, violet=database, amber=cloud/AWS, rose=security, orange=message bus), JetBrains Mono font, grid background. Best suited for…
kubernetes
Kubernetes operations expert for kubectl, pods, deployments, and debugging.
pentest-cloud-infrastructure
Cloud security posture management and container security assessment for AWS, Azure, GCP, and Kubernetes.