What is aidd-dev:08:for-sure?

An iterative work loop that keeps retrying a coding task until a stated success check passes.

Use it for requests such as “keep trying until done” when the task has a clear test or command that proves completion.

It helps with tasks where partial completion is not enough and progress must be verified.

aidd-dev:08:for-sure — Skill by ai-driven-dev

Install

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.

agentmods

npx agentmods add skills/ai-driven-dev/framework/08-for-sure

Any agent

npx skills add ai-driven-dev/framework --skill 08-for-sure

Clone the repo

git clone --depth 1 https://github.com/ai-driven-dev/framework

Made for: Claude Code, Codex.

Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 569 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00066	$0.00569
Opus 5	$0.00033	$0.00284
Sonnet 5	$0.00013	$0.00114
Haiku 4.5	$0.00007	$0.00057

Measured 2d ago against content hash d05c9108d689, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

aidd-dev:08:for-sure 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.

cli/tests/fixtures/framework-real/plugins/aidd-dev/skills/08-for-sure/SKILL.md · 50 lines

How it starts

The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.

For Sure

Autonomous loop that runs until a success condition is verified. Two phases: interactive pre-flight (human present), then autonomous execution (human gone). The agent auto-accepts everything, acts as the user, and never stops until success.

Context

Goal: Task's success_condition verified by running a command. All steps/acceptance criteria checked. File renamed to .done.md.
Tools required: Agent tool (spawning iterations), Read/Write/Edit (tracking file), task-specific tools.
Trigger: Manual — /for-sure.
Tracking file format: Uses the plan template from skill aidd-dev:01:plan (../../01-plan/assets/plan-template.md). Filename: aidd_docs/tasks/<task-name>.<status>.md.

Environment

None — task secrets are validated during pre-flight and documented in the tracking file.

Transversal rules

Single source of truth: IF information about the task exists THEN it lives in aidd_docs/tasks/<task-name>.<status>.md and nowhere else.
No repeated failures: IF approach X failed THEN do not try X again without a meaningful change.
Honesty over escape: IF success condition is not genuinely met THEN do not rename to .done.md.
Auto-accept: IF a decision, approval, or action is needed THEN act as the user. Create accounts, generate keys, approve prompts, install tools. Do not ask, do not hesitate, just do it.

Execution flow

Phase 1 — Interactive (human present)

actions/01-init-tracking.md — Pre-flight, create tracking file, spawn first autonomous agent.

Phase 2 — Autonomous (human gone)

actions/02-auto-accept.md — Auto-accept mode activation (Phase 3).
actions/03-autonomous-loop.md — Orchestrator: spawns one worker per step, verifies, checks/retries, evaluates success.

Actions

@actions/01-init-tracking.md
@actions/02-auto-accept.md
@actions/03-autonomous-loop.md

References

../../01-plan/assets/plan-template.md — tracking file format (frontmatter, phases, acceptance criteria, Log)

Read the full file on GitHub · 50 lines

Files

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.

Changes

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 · 50 lines · 66 tokens per session scan A d05c9108d689

Subscribe to this mod's changes

aidd-dev:08:for-sure is a skill published in the GitHub repository ai-driven-dev/framework (445 stars, last pushed 2d ago), licensed MIT. It adds 66 tokens to every session and 569 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.

Building agents agent agentic ai ai-driven-development commands context-engineering

skill-creator

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

bytedance/deer-flow · 64 tokens

claude-to-deerflow

Interact with DeerFlow AI agent platform via its HTTP API. Use this skill when the user wants to send messages or questions to DeerFlow for research/analysis, start a DeerFlow conversation thread, check DeerFlow status or health, list available models/skills/agents in DeerFlow, manage DeerFlow memory, upload files to…

bytedance/deer-flow · 111 tokens

find-skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

bytedance/deer-flow · 67 tokens

bootstrap

Generate a personalized SOUL.md through a warm, adaptive onboarding conversation. Trigger when the user wants to create, set up, or initialize their AI partner's identity — e.g., "create my SOUL.md", "bootstrap my agent", "set up my AI partner", "define who you are", "let's do onboarding", "personalize this AI", "make…

bytedance/deer-flow · 114 tokens

skill-reviewer

Reviews DeerFlow skill packages for readiness, triggers, safety boundaries, resources, and evidence. Invoke when users ask to audit, grade, or production-check an existing skill.

bytedance/deer-flow · 38 tokens

zeroclaw

Help users operate and interact with their ZeroClaw agent instance — through both the CLI (zeroclaw commands) and the REST/WebSocket gateway API. Use this skill whenever the user wants to: send messages to ZeroClaw, manage memory or cron jobs, check system status, configure channels or providers, hit the gateway API…

zeroclaw-labs/zeroclaw · 167 tokens