Borrowing it
Nothing to install: this file belongs to lxyer/multi-agent-collaboration-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lxyer/multi-agent-collaboration-system/main/.agents/skills/before-dev/SKILL.mdgit clone --depth 1 https://github.com/lxyer/multi-agent-collaboration-systemWrote 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/lxyer/multi-agent-collaboration-system/before-dev)<a href="https://agentmods.dev/skills/lxyer/multi-agent-collaboration-system/before-dev"><img src="https://agentmods.dev/badge/skills/lxyer/multi-agent-collaboration-system/before-dev/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/lxyer/multi-agent-collaboration-system/before-dev"><img src="https://agentmods.dev/badge/skills/lxyer/multi-agent-collaboration-system/before-dev.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00068 | $0.00352 |
| Opus 5.5 | $0.00027 | $0.00141 |
| Sonnet 5.5 | $0.00014 | $0.00070 |
| Haiku 4.5 | $0.00007 | $0.00035 |
Grade A, and why
before-dev 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.
This is a copy
89% identical to trellis-before-dev — 20 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Read the relevant development guidelines before starting your task.
Execute these steps:
-
Discover packages and their spec layers:
python3 ./.trellis/scripts/get_context.py --mode packages -
Identify which specs apply to your task based on:
- Which package you're modifying (e.g.,
cli/,docs-site/) - What type of work (backend, frontend, unit-test, docs, etc.)
- Which package you're modifying (e.g.,
-
Read the spec index for each relevant module:
cat .trellis/spec/<package>/<layer>/index.mdFollow the "Pre-Development Checklist" section in the index.
-
Read the specific guideline files listed in the Pre-Development Checklist that are relevant to your task. The index is NOT the goal — it points you to the actual guideline files (e.g.,
error-handling.md,conventions.md,mock-strategies.md). Read those files to understand the coding standards and patterns. -
Always read shared guides:
cat .trellis/spec/guides/index.md -
Understand the coding standards and patterns you need to follow, then proceed with your development plan.
This step is mandatory before writing any code.
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 · 35 lines · 68 tokens per session scan A 8ba9c9703b6f
before-dev is a skill published in the GitHub repository lxyer/multi-agent-collaboration-system (1 stars, last pushed 6mo ago), licensed MIT. It adds 68 tokens to every session and 352 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to trellis-before-dev, differing in 20 lines, and is treated as a copy.
Other skills, from other repositories
meta-cognition-parallel
An experimental tool for analysing a question or problem in parallel across three layers.
rust-learner
Use when asking about Rust versions or crate info. Keywords: latest version, what's new, changelog, Rust 1.x, Rust release, stable, nightly, crate info, crates.io, lib.rs, docs.rs, API documentation, crate features, dependencies, which crate, what version, Rust edition, edition 2021, edition 2024, cargo add, cargo…
rust-router
A routing skill for Rust development questions, including errors, design choices, comparisons, and coding tasks involving Rust tools and packages.
m07-concurrency
A guide to running work at the same time in Rust, either on threads or through async tasks. It covers shared data, channels, locks, atomics, futures, and common problems such as races and deadlocks.
domain-embedded
A set of guidance for developing embedded Rust software, such as firmware running directly on a microcontroller without a full operating system.
domain-ml
A set of guidance for building machine-learning and artificial-intelligence applications in Rust. Machine learning uses data and models to make predictions or other decisions.