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/promptpartner/agentsmith/autonomous-runnpx skills add PromptPartner/agentsmith --skill autonomous-rungit clone --depth 1 https://github.com/PromptPartner/agentsmithWrote 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/promptpartner/agentsmith/autonomous-run)<a href="https://agentmods.dev/skills/promptpartner/agentsmith/autonomous-run"><img src="https://agentmods.dev/badge/skills/promptpartner/agentsmith/autonomous-run.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.00053 | $0.00824 |
| Opus 5 | $0.00026 | $0.00412 |
| Sonnet 5 | $0.00011 | $0.00165 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
autonomous-run 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 today.
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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous run — bounded overnight execution
This skill is for a finite approved implementation, not a recurring watcher. For recurring work use the autonomous-loops profile. For unresolved product or architecture decisions, run Wayfinder first.
Hard gate
Do not begin implementation unless all of these are true:
- The terminal spec is committed under
docs/specs/withstatus: accepted,accepted_by, andaccepted_at. An agent may author onlystatus: draft. - A separate implementation-ticket ID is named. The decision ticket is not executable work.
- The operator explicitly invokes or authorizes
start. Producing or checking a spec never self-authorizes implementation.
Linear and every other external system still follow the installed write-consent rule. The v1 controller has no external-write adapter at all.
Prepare the contract
If scripts/autonomous-run.py exists, use it. Its installed template is
.harness/templates/autonomous-run.json (the harness source checkout uses
templates/autonomous-run.json):
python3 scripts/autonomous-run.py prepare --run-id <short-id> --spec docs/specs/<name>.md --ticket <implementation-ticket> --maker codex --checker claude --template .harness/templates/autonomous-run.json
This only creates a manifest. Review its exact allowed/denied paths, verifier, models, attempt cap,
wall-clock limit, budgets, and optional scope.resources keys such as port:3000 or
db:local/test. Resource keys coordinate cooperating local runs; they do not replace operating-
system port binding or database isolation. Commit the manifest before execution; the controller
refuses an uncommitted contract. Concurrent worktrees share writable Git metadata needed for local
commits, so this guard prevents accidental collisions between cooperating runs; it is not a
security boundary for mutually untrusted makers.
Start and supervise
Only after explicit operator authorization:
python3 scripts/autonomous-run.py start .harness/runs/<short-id>.json
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.
- today Changed · +10 lines 3ca93eeedab0
- 4d ago First seen · 63 lines · 53 tokens per session scan A 4359e1d36e18
autonomous-run is a skill published in the GitHub repository PromptPartner/agentsmith (185 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 824 once invoked, about $0.0003 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-30.
Other skills, from other repositories
crit-cli
Use when an agent needs to author or reply to crit inline comments programmatically (including multi-agent workflows commenting on shared code/plans/docs/proposals), publish or unpublish a crit review with crit share, sync a crit review to or from a GitHub PR or GitLab MR, or read/interpret a crit review JSON file.…
crit
Review code changes, a plan, a live page (running dev server), or a local HTML file with Crit inline comments and structured human feedback. Use only when the user explicitly invokes /crit or directly asks to use Crit; a generic review request does not count.
crit-story
Author a crit story only when the user explicitly invokes /crit-story or directly asks you to generate a crit story. Do not infer this skill from generic review, PR, or diff-review requests.
truthmark-sync
Use automatically at finish-time after functional code changes, or explicit /truthmark-sync, $truthmark-sync, or /truthmark:sync. Skip docs-only, formatting-only, behavior-preserving renames, missing config, and no-code changes. Not for doc-first realization or manual topology design.
truthmark-document
Use when the user asks to document existing implemented behavior, or Sync, Check, or Structure finds implemented behavior missing canonical truth. Not for functional-code changes, doc-first implementation, or topology repair that needs Structure.
truthmark-realize
Use when the user explicitly asks to realize Truthmark truth docs into code, including /truthmark-realize, $truthmark-realize, or /truthmark:realize. Not for syncing docs after code changes, documenting existing code, topology repair, or truth audits.