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 ericrisco/rsc-harness --skill no-code-appgit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/no-code-app)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/no-code-app"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/no-code-app/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/ericrisco/rsc-harness/no-code-app"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/no-code-app.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 15 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00087 | $0.02755 |
| Opus 5.5 | $0.00035 | $0.01102 |
| Sonnet 5.5 | $0.00017 | $0.00551 |
| Haiku 4.5 | $0.00009 | $0.00276 |
Grade A, and why
no-code-app 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 1mo 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
No-code app
You are deciding whether to build an app on a visual platform, which platform, how to model it, and where the wall is. No-code is not "the easy way" — it is a trade: you buy speed-to-first-user and pay it back in logic ceilings and metered cost. Your job is to make that trade with eyes open.
Decide the exit before you build the entrance. If you cannot describe how you would leave, you are not building an MVP — you are building a hostage.
No-code wins on speed-to-first-user — a working app in days, no deploy pipeline. That is the only thing it reliably wins. It dies on deep conditional logic and on scale economics: many-branch workflows get unmaintainable, and metering turns a $29 bill into a $400 one without warning.
Step 0: is no-code even the right tool?
Run this gate before touching any builder. If any line is a clear yes, route out — do not rationalize staying.
| If the user really wants... | Stop and go to |
|---|---|
| A hand-written app, full control over code | ../nextjs/SKILL.md (or ../react/SKILL.md) |
| A commerce storefront, products + checkout | ../shopify/SKILL.md |
| A content site / blog / CMS | ../wordpress/SKILL.md |
| To wire SaaS tools together, no app UI | ../automation-flows/SKILL.md |
| A spreadsheet as the deliverable itself | ../spreadsheet-ops/SKILL.md |
| A Notion workspace, not a published app | ../notion-connector/SKILL.md |
No-code is the right tool when ALL hold: there is a real app UI (screens + data + logic), the logic is mostly CRUD + a handful of rules, time-to-launch matters more than scale today, and you accept the platform owns your runtime. If logic is the heart of the product (pricing engine, matching algorithm, real-time anything), no-code is wrong even if the UI is simple — write code.
Pick the platform
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.
- 1mo ago First seen · 146 lines · 87 tokens per session scan A dca492256782
no-code-app is a skill published in the GitHub repository ericrisco/rsc-harness (247 stars, last pushed yesterday), licensed MIT. It adds 87 tokens to every session and 2,755 once invoked, about $0.0003 per session on Opus 5.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-03.
Other skills, from other repositories
starting-a-new-project
Use when the workspace is empty, has no code, and the user brings a raw project idea. Normally reached via setting-up-a-project; not for an existing project.
file-a-task
File work into nohuman (taskadd) and check on it (taskstatus) via the nohuman MCP bridge, instead of doing the work inline.
durable-work
Picks the board over sub-agents for cross-turn work.
ops-standup
Cross-repo morning briefing. Aggregation of recent commits, PRs, CI, blockers and priorities of the day. Trigger when the user wants a standup, an activity summary, or to know what happened.
work-batch
Sequential execution of user stories from a PRD file. Autonomous mode that implements and commits each story one by one. Trigger when the user wants to process a backlog, execute multiple stories, or launch an autonomous mode.
all-hands
Convene the relevant SpecRoute implementation agents to plan, collaborate, implement, and review a piece of work end-to-end. Engages only the specialists the work actually touches, runs autonomously through planning into implementation and review, and accepts free-text work or a path to a PRD / spec / issue file.…