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/lxyer/multi-agent-collaboration-system/record-sessiongit 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/commands/lxyer/multi-agent-collaboration-system/record-session)<a href="https://agentmods.dev/commands/lxyer/multi-agent-collaboration-system/record-session"><img src="https://agentmods.dev/badge/commands/lxyer/multi-agent-collaboration-system/record-session.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.00000 | $0.00589 |
| Opus 5 | $0.00000 | $0.00295 |
| Sonnet 5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
record-session 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.
This is a copy
88% identical to record-session — 5 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!] Prerequisite: This command should only be used AFTER the human has tested and committed the code.
Do NOT run git commit directly — the scripts below handle their own commits for .trellis/ metadata. You only need to read git history (git log, git status, git diff) and run the Python scripts.
Record Work Progress
Step 1: Get Context & Check Tasks
python3 ./.trellis/scripts/get_context.py --mode record
[!] Archive tasks whose work is actually done — judge by work status, not the status field in task.json:
- Code committed? → Archive it (don't wait for PR)
- All acceptance criteria met? → Archive it
- Don't skip archiving just because
statusstill saysplanningorin_progress
python3 ./.trellis/scripts/task.py archive <task-name>
Step 2: One-Click Add Session
# Method 1: Simple parameters
python3 ./.trellis/scripts/add_session.py \
--title "Session Title" \
--commit "hash1,hash2" \
--summary "Brief summary of what was done"
# Method 2: Pass detailed content via stdin
cat << 'EOF' | python3 ./.trellis/scripts/add_session.py --stdin --title "Title" --commit "hash"
| Feature | Description |
|---------|-------------|
| New API | Added user authentication endpoint |
| Frontend | Updated login form |
**Updated Files**:
- `packages/api/modules/auth/router.ts`
- `apps/web/modules/auth/components/login-form.tsx`
EOF
Auto-completes:
- [OK] Appends session to journal-N.md
- [OK] Auto-detects line count, creates new file if >2000 lines
- [OK] Auto-detects Branch context (
--branchoverride; otherwise Branch = task.json -> current git branch; missing values are omitted gracefully) - [OK] Updates index.md (Total Sessions +1, Last Active, line stats, history)
- [OK] Auto-commits .trellis/workspace and .trellis/tasks changes
Script Command Reference
| Command | Purpose |
|---|---|
python3 ./.trellis/scripts/get_context.py --mode record |
Get context for record-session |
python3 ./.trellis/scripts/add_session.py --title "..." --commit "..." |
One-click add session (recommended, branch auto-complete) |
python3 ./.trellis/scripts/task.py archive <name> |
Archive completed task (auto-commits) |
python3 ./.trellis/scripts/task.py list |
List active tasks |
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 · 63 lines · 0 tokens per session scan A 33b5626fcf03
record-session is a command published in the GitHub repository lxyer/multi-agent-collaboration-system (1 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 589 tokens. A static security scan graded it A with 0 findings. It is 88% identical to record-session, differing in 5 lines, and is treated as a copy.
Other commands, from other repositories
commit
See .opencode/skills/git-commit/SKILL.md for commit format rules.
save
Save current session. Writes a session log with what was done, decisions made, and what's pending. Optional: commit & push.
plan-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
fest-commit
Commit changes with festival traceability metadata.
catchup
Restore context after /clear by summarizing recent work and project state.
commit
Generate a conventional commit message for staged changes.