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 OKHP3/skillz --skill okhp3-replit-build-in-publicgit clone --depth 1 https://github.com/OKHP3/skillzWrote 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/okhp3/skillz/okhp3-replit-build-in-public)<a href="https://agentmods.dev/skills/okhp3/skillz/okhp3-replit-build-in-public"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/okhp3-replit-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/okhp3/skillz/okhp3-replit-build-in-public"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/okhp3-replit-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.00105 | $0.02573 |
| Opus 5 | $0.00053 | $0.01287 |
| Sonnet 5 | $0.00021 | $0.00515 |
| Haiku 4.5 | $0.00011 | $0.00257 |
Grade A, and why
okhp3-replit-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 6d 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
okhp3-replit-build-in-public
OverKill Hill P³ · overkillhill.com · github.com/OKHP3
Building in public on Replit is not just about shipping code — it is about making your process visible. This skill covers the full arc: how to organise what you have built so judges can evaluate it quickly, how to deploy it to two public surfaces, how to maintain narrative continuity across many build sessions, and how to make your commit history a readable story.
Scope
| In scope | Out of scope |
|---|---|
| Canvas as a judge showcase board | Canvas callback mechanics — read the canvas skill |
| Artifact selection for judges | GitHub Pages mechanics — read okhp3-vite-github-pages |
| Dual deployment setup | Replit deployment mechanics — read the deployment skill |
| Session handoff conventions | Multi-artifact monorepo rules — read okhp3-replit-multi-artifact |
| Commit-message discipline | Individual artifact build instructions |
The two modes of the canvas
Building mode — the canvas is a work surface. Iframes are scattered, some are building, labels are missing. This is fine during development; judges never see it.
Judging mode — the canvas is a showcase board. Every iframe is live, zones are labeled and numbered, a focusCanvasShapes call navigates judges to the layout automatically.
Switch to judging mode before every public review. The canvas is the first thing a judge sees in the Replit workspace.
Canvas organisation for judges
Hero row
The top strip of the board. Place your three primary deliverables here — the live interactive artifact (game, app, tool), the portfolio/pitch deck, and the showcase video. These are the artifacts judges interact with directly.
y = 100
x positions: 0, (w1 + 80), (w1 + 80 + w2 + 80), ...
Section label above the hero row:
y = 20, h = 60, color = grey
text = "SYSTEM ARTIFACTS — live app · portfolio deck · cinematic video"
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.
- 6d ago First seen · 254 lines · 105 tokens per session scan A 25536aa8c55c
okhp3-replit-build-in-public is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed today), licensed MIT. It adds 105 tokens to every session and 2,573 once invoked, about $0.0005 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-09-05.
Other skills, from other repositories
release-skills
A release workflow for preparing and publishing a new version of a software project. A release is a named version that may include updated version files, release notes, tags, or a GitHub Release.
ship
Commit, push, and optionally create or update a PR for the current staged changes. Use when the user asks to "ship", "ship it", "ship changes", "commit push and PR", or "ship this".
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…
stage
Stage implementation changes for commit with precise file selection. Use when the user asks to "stage changes", "stage files", "add files to staging", or "prepare changes for commit".
semantic-szz-analyzer
Identify bug-introducing commits using semantic analysis that extends traditional SZZ algorithm. Distinguishes semantic changes from refactorings or code movements using control-flow and data-flow similarity analysis. Use when analyzing bug-fix commits to trace back to bug-introducing changes, investigating software…
szz-bug-introducing-commit-identifier
Identifies bug-introducing commits using SZZ-style analysis based on bug-fixing commits, commit history, and code blame information. Use this skill when you need to trace bugs back to their origin, identify which commits introduced bugs, analyze bug-fix commits to find root causes, perform software repository mining…