A guide to the repository’s repeatable development workflows, stored as Taskfile tasks. It covers Alef code generation, project and binding builds, end-to-end tests, cleanup, and known build traps.

Use it when changing Alef or core code, regenerating bindings, running end-to-end test cycles, cleaning build artifacts, or diagnosing related failures.

It helps developers use the repository’s intended commands instead of assembling risky ad-hoc command sequences. It also explains issues involving mock servers, stale shared libraries, generated tests, and cached files.

dev-cycle — Skill for Claude Code and Codex by xberg-io: A guide to the repository’s repeatable development workflows, stored…

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/xberg-io/crawlberg/dev-cycle

Any agent

npx skills add xberg-io/crawlberg --skill dev-cycle

Clone the repo

git clone --depth 1 https://github.com/xberg-io/crawlberg

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/xberg-io/crawlberg/dev-cycle.svg)](https://agentmods.dev/skills/xberg-io/crawlberg/dev-cycle)

Your own site

<a href="https://agentmods.dev/skills/xberg-io/crawlberg/dev-cycle"><img src="https://agentmods.dev/badge/skills/xberg-io/crawlberg/dev-cycle.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 635 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.00089	$0.00635
Opus 5	$0.00044	$0.00318
Sonnet 5	$0.00018	$0.00127
Haiku 4.5	$0.00009	$0.00064

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

Security

Grade A, and why

dev-cycle 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 4d 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.

.ai-rulez/skills/dev-cycle/SKILL.md · 49 lines

What it actually says

Iteration loops are codified as Taskfile tasks. Prefer them over ad-hoc commands.

After alef changes

task alef:install              # cargo install --path ../alef/crates/alef-cli
task alef:generate             # alef all --clean --format=false
task alef:format               # explicit Alef formatting; task format excludes this
VERSION=0.15.30 task alef:bump # bump pin in alef.toml + reinstall + regen

After crawlberg-core changes

task build          # core-only
task build:bindings # all bindings
task build:all      # core + all bindings

E2E cycles

task e2e:generate # regenerate all language test suites from fixtures
task e2e:build    # build bindings and the generated mock-server for e2e
task e2e:test     # run generated e2e suites
task e2e:all      # generate + build + run generated e2e suites

Cleanup

task clean           # per-language artifacts
task clean:workspace # cargo target + alef IR cache + legacy mock-server bins
task clean:e2e       # venvs, node_modules, _build, lockfiles, vendor/
task clean:full      # all of the above

Gotchas (codified, but worth knowing)

Two mock-server binaries. tools/mock-server is legacy/unused; e2e/rust/src/main.rs is alef-generated and the binary all language conftests actually spawn. task e2e:build builds the right one at e2e/rust/target/release/mock-server.
Python venv stale .so. After task python:build:dev, the e2e venv at e2e/python/.venv keeps a stale extension. task python:cycle runs uv sync --reinstall to refresh.
Elixir precompiled NIF. Rustler's precompiled binary is tagged at the package's release version and lags local source. CRAWLBERG_BUILD=1 is set in .task/languages/elixir.yml::e2e:test so the e2e suite always builds the NIF from local source.
Generated e2e files. e2e/<lang>/ is alef-generated — never hand-edit. Modify fixtures or alef codegen, then task alef:generate.

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.

4d ago First seen · 49 lines · 89 tokens per session scan A 27de14aee517

Subscribe to this mod's changes

dev-cycle is a skill published in the GitHub repository xberg-io/crawlberg (168 stars, last pushed today), licensed MIT. It adds 89 tokens to every session and 635 once invoked, about $0.0004 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.

C# and .NET Debugging Go Java Testing crawling elixir ffi

java-clean-code

Complete Clean Code reference for Java 21+ in one skill — naming, methods, comments, general quality, and tests, with modern idioms (records, sealed types, pattern matching, Optional, streams). Use when writing, reviewing, or refactoring any Java code and you want the whole catalog at once rather than one focused area.

CasLubbers/code-design-skills · 72 tokens

java-clean-functions

Enforces method design in Java 21+ — small methods that do one thing, at most three parameters, no boolean flag arguments, no null returns or arguments, and command-query separation. Use when writing or refactoring Java methods and constructors, and when the code shows long methods, parameter lists of four or more…

CasLubbers/code-design-skills · 0 tokens

java-clean-general

Enforces general code quality in Java 21+ — DRY, no magic numbers, immutability by default, sealed hierarchies and pattern matching over instanceof chains, encapsulation over getters and setters, and streams used where they clarify. Use when reviewing or refactoring Java for quality, and when the code shows…

CasLubbers/code-design-skills · 0 tokens

go-api-design

Enforces Go package and API design — small exported surfaces, packages named for what they provide, functional options instead of growing constructors, context first, no init side effects, and changes that stay backward compatible. Use when creating or restructuring Go packages, designing an exported API or library…

CasLubbers/code-design-skills · 104 tokens

go-concurrency

Enforces safe Go concurrency — every goroutine has a known stop condition, context propagates cancellation, channel ownership and direction are explicit, and shared state is protected or not shared. Use when writing or reviewing Go that starts goroutines, uses channels, sync primitives, or context, and when the user…

CasLubbers/code-design-skills · 106 tokens

go-idiom

Enforces idiomatic Go style — name length scaled to scope, no stutter, useful zero values, guard clauses, correct defer placement, composition over inheritance, and doc comments in the required form. Use when writing, reviewing, or refactoring any Go code, and when the user asks whether something is idiomatic…

CasLubbers/code-design-skills · 112 tokens