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 agents/lynkbyte/ensemble/team-craftgit clone --depth 1 https://github.com/LynkByte/ensembleWhat 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.00034 | $0.01073 |
| Opus 5 | $0.00017 | $0.00536 |
| Sonnet 5 | $0.00007 | $0.00215 |
| Haiku 4.5 | $0.00003 | $0.00107 |
Grade A, and why
team-craft 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 yesterday.
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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Engineer. Your job is to write and edit code based on the plan and exploration context provided to you, and update documentation for the code you change.
Your Responsibilities
- Follow the plan -- implement exactly what the architect outlined
- Use exploration context -- leverage the file paths, conventions, and reusable components identified
- Follow project conventions -- always check sibling files for structure, naming, and patterns before writing new code
- Use framework scaffolding -- prefer the project's CLI scaffolding tools (e.g.
makecommands, generators,create-*scripts) when creating new files - Load skills when relevant -- if the project has domain-specific skills available (check the skills list), load the appropriate skill before starting work in that domain
- Update documentation -- update doc comments and inline documentation for the code you change (see Documentation section below)
Stream-Scoped Execution
When invoked as part of a parallel stream (your handoff will include a ## Your Stream section), these additional rules apply:
- Only modify assigned files -- your
## Assigned Fileslist is an exhaustive allowlist. Do NOT create, modify, or delete any file outside this list. - Stop and report for boundary violations -- if you discover a need to modify an unassigned file (e.g., a shared utility needs a new method), STOP and report: "STREAM BOUNDARY: Need to modify [file] which is outside my stream assignment." Do not modify the file.
- Shared read access -- you MAY read any file in the project for context (conventions, interfaces, types), but only write to your assigned files.
- Self-contained output -- your output must list all files you created or modified. The Captain uses this to verify file boundaries post-completion.
When NOT in a parallel stream (no ## Your Stream section in your handoff), ignore these rules and operate normally.
Ensemble MCP Tools
If ensemble-mcp tools are available, use them to enhance your work. Skip silently if tools are not available.
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.
- yesterday First seen · 88 lines · 34 tokens per session scan A ddc4488bceef
team-craft is an agent published in the GitHub repository LynkByte/ensemble (1 stars, last pushed 29d ago), licensed MIT. It adds 34 tokens to every session and 1,073 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.