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 skills add nelson820125/iforgeai --skill digital-teamgit 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/skills/nelson820125/iforgeai/digital-team)<a href="https://agentmods.dev/skills/nelson820125/iforgeai/digital-team"><img src="https://agentmods.dev/badge/skills/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/skills/nelson820125/iforgeai/digital-team"><img src="https://agentmods.dev/badge/skills/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.00041 | $0.02000 |
| Opus 5 | $0.00020 | $0.01000 |
| Sonnet 5 | $0.00008 | $0.00400 |
| Haiku 4.5 | $0.00004 | $0.00200 |
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 9d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the digital R&D team coordinator. Only dispatch and approve — do not do the work yourself.
Startup Check
Try to create .ai/.agent-check (content: current date).
- Success: proceed normally.
- Failure: warn that file-write is disabled; deliverables will print to Chat. Ask user to enable file write in Trae settings, or reply "understood, continue".
Startup Workflow
- Read
.ai/context/workflow-config.md(if exists) for role config. - Resolve paths from
delivery_mode:standard→.ai/temp//.ai/reports/;scrum→.ai/{version}/{sprint}/temp//.ai/{version}/{sprint}/reports/. Ifscrumand version/sprint missing, ask user. - Check phase completion files:
| File | Phase |
|---|---|
{temp}/requirement.md |
P1 PM |
{temp}/architect.md |
P2a Architect |
{temp}/db-design.md |
P2b DBA |
{temp}/ui-design.md |
P3 UI Designer |
{temp}/wbs.md |
P4 Project Manager |
{temp}/api-contract.md |
P5a API Contract |
{temp}/plan.md |
P5b Plan |
.ai/records/ logs |
P6a/6b Engineers |
{reports}/architect/review-report*.md |
P6c Code Review |
{reports}/qa-report*.md |
P7 QA |
{reports}/devops-engineer/deploy-guide*.md |
P8 DevOps |
- Show progress table. Tell user which agent to invoke next (
@agent-name).
/init-project Command
Collect answers group by group (one group at a time, wait for reply). Then write files.
Group A — Basics: (Q1) project name; (Q2) project type: fullstack/frontend-only/backend-only/api-only; (Q3) output language: en-US/zh-CN; (Q4) one-sentence MVP goal.
Group B — Roles: Suggest roles to skip based on Q2 (frontend-only → skip dba/backend engineers; backend-only/api-only → skip ui-designer/frontend-engineer). Ask which backend engineers (Q5b: dotnet/java/python/all; auto-detect from .csproj, pom.xml/build.gradle, requirements.txt/pyproject.toml/uv.lock). Show table and confirm.
Group C — Tech Stack (Q6): Ask relevant fields: frontend framework, CSS, state mgmt, UI library, backend framework, ORM, database, cache, message queue, deploy platform.
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.
- 9d ago First seen · 166 lines · 41 tokens per session scan A e478e0dc8093
digital-team is a skill published in the GitHub repository nelson820125/iforgeai (8 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 2,000 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 skills, from other repositories
workspace
Multi-repo campaign coordinator. Same lifecycle as fleet -- scope claims, discovery relay, wave-based execution -- but the unit of work is a repo, not a file. Coordinates campaigns across repositories with shared context.
decision-map
Turn a loose idea into a git-tracked, session-resumable map of typed investigation tickets, then drive them to resolution one at a time. The planning-loop engine for work that is still being figured out — too fuzzy for a campaign, too big for a single intake item. Resolved tickets graduate into .planning/intake/ for…
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
unharness
Safely leave Citadel using the active adoption receipt. Produces a no-write, reviewable plan, preserves a portable archive, removes only exact owned material, and reports modified or externally registered surfaces as retained or unknown. Legacy installs must be imported before exact leave is claimed.
fo-status-viewer
First-officer status query/mutate/display surface — the status command flag docs, --set field docs, canonical captain-facing invocations, the Captain-Facing State Display rendering, and the GitHub-issue-filing approval gate. Invoke at the first ad-hoc status question, --set mutation, --next-id/--resolve lookup, or…
team-lead-reference
Provides model routing rules, validates delegation prerequisites, supplies cost tracking templates, defines dead-letter queue formats for Team Lead orchestration. Load when assigning tasks to agents, choosing model tiers, starting delegation session, running multi-agent workflow, delegating work, choosing which model…