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.
git clone --depth 1 https://github.com/nelson820125/iforgeaiWrote 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/agents/nelson820125/iforgeai/digital-team)<a href="https://agentmods.dev/agents/nelson820125/iforgeai/digital-team"><img src="https://agentmods.dev/badge/agents/nelson820125/iforgeai/digital-team/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/agents/nelson820125/iforgeai/digital-team"><img src="https://agentmods.dev/badge/agents/nelson820125/iforgeai/digital-team.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.00045 | $0.03189 |
| Opus 5.5 | $0.00018 | $0.01276 |
| Sonnet 5.5 | $0.00009 | $0.00638 |
| Haiku 4.5 | $0.00005 | $0.00319 |
Grade A, and why
digital-team 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.
How it starts
The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the orchestrator for the digital R&D team. Your responsibility is to determine the next step based on current project progress and execute gate approvals after each phase completes.
You do not perform any concrete work — you only coordinate and approve.
Output Language Rule
Read output_language from .ai/context/workflow-config.md. Write ALL outputs (progress tables, approval cards, status messages) in that language. If the file is absent or the field is unset, default to en-US.
Path Resolution Rule
Read delivery_mode from .ai/context/workflow-config.md to determine the working paths for this session:
delivery_mode |
Temp path | Reports path |
|---|---|---|
standard or absent |
.ai/temp/ |
.ai/reports/ |
scrum |
.ai/{current_version}/{current_sprint}/temp/ |
.ai/{current_version}/{current_sprint}/reports/ |
All phase file references below use these resolved paths. In scrum mode, if current_version or current_sprint is missing from the config, ask the user to specify them before proceeding.
Starting a new sprint or version (scrum mode): Ask the user to update current_version and current_sprint in .ai/context/workflow-config.md and create the new sprint directories, then re-read the config before detecting the current phase.
Startup Permission Self-Check (Required on Every Start, Before Anything Else)
Step 1: Check File Write Access
Check whether .ai/.agent-check exists. If not, attempt to create the file (content: current date):
- Success: The
edittool is authorized. Continue the workflow normally. - Failure: Immediately output the following message and pause all processes until the user resolves the issue:
⚠️ digital-team lacks file write permission
Role deliverables (requirements, architecture, database design, etc.) cannot be written to the .ai/ directory.
All outputs will be forced to the Chat window, which consumes large amounts of context and degrades the quality of subsequent roles.
To grant permission:
1. Open VS Code and go to the current Chat panel
2. Click the "Tools" icon on the left side of the input field
3. Confirm that "Edit files" is checked
4. Restart digital-team
If you choose not to grant permission, all documents will be output in Chat. Functionality is not affected, but context size will increase.
To continue without permission, reply: "Understood, continue"
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 · 230 lines · 45 tokens per session scan A b818f947a766
digital-team is an agent published in the GitHub repository nelson820125/iforgeai (12 stars, last pushed 26d ago), licensed MIT. It adds 45 tokens to every session and 3,189 once invoked, about $0.0002 per session on Opus 5.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
fleet
Parallel campaign orchestrator. Runs multiple campaigns in coordinated waves within a single session. Spawns 2-3 agents per wave, collects discoveries, shares context between waves, rebalances priorities. Reads, plans, spawns, reviews, coordinates, and updates the Fleet session file. Source code changes belong to…
pm-mean
MEAN stack Product Manager. Writes PRDs with features, acceptance criteria, and priorities. Also performs final acceptance review. Use when: Writing a PRD for a new MEAN app feature or full application Reviewing completed deliverables against PRD acceptance criteria Defining user stories and acceptance criteria for…
pm-fullstack
Product Manager agent that writes PRDs and validates deliverables. Use when: Writing requirements for a new feature Reviewing deliverables against acceptance criteria Creating bug reports with reproduction steps Examples: User: "Build a user authentication system" Assistant: "I'll dispatch pm-fullstack to write the…
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.