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 commands/rajconnects/founder-stack/mission-tickgit clone --depth 1 https://github.com/rajconnects/founder-stackWhat 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.00049 | $0.00731 |
| Opus 5 | $0.00024 | $0.00365 |
| Sonnet 5 | $0.00010 | $0.00146 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
mission-tick 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 2d 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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are firing one tick of an in-flight mission's autonomous loop. This command runs the tick procedure directly in the main agent thread — the procedure dispatches feature-worker, scrutiny-validator, design-auditor, schema-analyst, user-flow-tester, docs-auditor, and memory-broker via the Task tool. Claude Code blocks sub-agents from spawning further sub-agents, so the tick procedure must run as the main thread, not a sub-agent.
Entry expectation: this command should be invoked via /loop /mission-tick <id> — that puts the session into /loop dynamic mode, which is what makes the tick procedure's ScheduleWakeup calls actually fire. If you were invoked as a bare /mission-tick <id> (no /loop prefix), wakeups will be no-ops and the mission will stall after one tick.
Arguments: $ARGUMENTS
Steps
-
If
$ARGUMENTSis empty: printERROR: /mission-tick requires a mission idand stop. -
Read
.claude/project.json→mission_root. Confirm<mission_root>/<id>/state.jsonexists. If not: printERROR: no mission state found at <path>. Aborting tick.and stop. -
Read
.claude/procedures/v1/mission-tick.mdand execute it in this main agent thread. Pass:MISSION_ID:<id>from$ARGUMENTS
The procedure handles cap checks, dispatches the next step (worker → scrutiny+design+schema in parallel → user-test → handoff), saves state, and either calls
ScheduleWakeup(local pace) or returns silently (cron pace). On the last feature's handoff, it runs the Completion section (docs-audit, memory write, PR handoff). -
After the procedure returns, capture its return line. Shape:
<id> | step <step> | <verdict-summary> | pace <pace> | status <status>. Print it verbatim. -
Cron pace cleanup. If the return shows
pace cronANDstatusis one ofcompleted,aborted, orblocked: invoke the/scheduleskill via the Skill tool to delete the routine namedmission-<id>. The mission's cron schedule should not keep firing after a terminal state. If routine deletion fails (already gone, schedule skill unreachable), log a warning but don't fail the tick — the next cron fire will just see terminal status and exit cleanly without doing work.
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.
- 2d ago First seen · 32 lines · 49 tokens per session scan A 6d2f7df5e7c8
mission-tick is a command published in the GitHub repository rajconnects/founder-stack (2 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 731 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.