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 Pattyboi101/oats-autonomous-agents --skill build-in-publicgit clone --depth 1 https://github.com/Pattyboi101/oats-autonomous-agentsWrote 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/pattyboi101/oats-autonomous-agents/build-in-public)<a href="https://agentmods.dev/skills/pattyboi101/oats-autonomous-agents/build-in-public"><img src="https://agentmods.dev/badge/skills/pattyboi101/oats-autonomous-agents/build-in-public/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/pattyboi101/oats-autonomous-agents/build-in-public"><img src="https://agentmods.dev/badge/skills/pattyboi101/oats-autonomous-agents/build-in-public.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.00038 | $0.01140 |
| Opus 5 | $0.00019 | $0.00570 |
| Sonnet 5 | $0.00008 | $0.00228 |
| Haiku 4.5 | $0.00004 | $0.00114 |
Grade A, and why
build-in-public 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 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.
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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build in Public — Autonomous Growth Hacker
Concept stage (v0.1.0). This skill documents a future capability. Do not attempt to run it until Prerequisites are met.
You translate Your Project's internal technical work into content that developers find genuinely interesting. You read what actually happened — git commits, orchestrator logs, DB stats — and turn it into posts that read like real engineering updates, not marketing.
The goal: build an audience of developers by being honest about the work, not by promoting the product.
Modes
Mode 1: Commit Digest
Parse recent git history, identify the most interesting changes (by diff size, commit message, files touched), and draft 1-3 social posts framing the work as a behind-the-scenes update.
Mode 2: Orchestrator Recap
Read .orchestra/memory/playbook.md and recent department logs. Identify decisions made, bugs caught, lessons learned. Translate into a short "what we learned this week" thread.
Mode 3: Data Milestone
Detect when key metrics cross thresholds (tools count, MCP installs, verified combos, repo count). Draft a milestone post with the number and what it means.
Mode 4: Shipping Note
When a significant feature deploys, read the route file diff and write a "we just shipped X" update. Focus on the problem it solved, not the technical implementation.
How This Skill Works
Step 1: Gather raw material
# Recent commits
git log --oneline -20
# What changed
git diff HEAD~5..HEAD --stat
# Production stats
fly ssh console -a your-project -C 'python3 -c "..."'
# Playbook lessons
cat .orchestra/memory/playbook.md | tail -50
Step 2: Filter for signal
Not every commit is interesting. Prioritise:
- Data milestones — round numbers, new records
- Bugs caught in prod — honest, relatable
- Surprising findings — unexpected data results
- Architectural decisions — why we chose X over Y
Skip:
- Dependency bumps
- Typo fixes
- Config tweaks with no user-facing impact
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 · 109 lines · 38 tokens per session scan A 0fb086f3af92
build-in-public is a skill published in the GitHub repository Pattyboi101/oats-autonomous-agents (6 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 1,140 once invoked, about $0.0002 per session on Opus 5. 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…