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 FerroxLabs/ijfw --skill ijfw-teamgit clone --depth 1 https://github.com/FerroxLabs/ijfwWrote 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/ferroxlabs/ijfw/ijfw-team)<a href="https://agentmods.dev/skills/ferroxlabs/ijfw/ijfw-team"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-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/ferroxlabs/ijfw/ijfw-team"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 5 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00043 | $0.03601 |
| Opus 5.5 | $0.00017 | $0.01440 |
| Sonnet 5.5 | $0.00009 | $0.00720 |
| Haiku 4.5 | $0.00004 | $0.00360 |
Grade A, and why
ijfw-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 — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IJFW Team Assembly
Assembles a project-specific operating team. Team Assembly is project-agnostic: it works for software, books, content, design, research, business strategy, education, operations, and mixed projects.
Do not treat every team as a code-generation swarm. Generate the agents plus the operating contracts that let those agents coordinate around artifacts, claims, reviews, and handoffs.
CLI entry point: ijfw team init [--archetype <type>] [--name <team-name>] [--brief <text>].
ijfw team is the skill/workflow trigger; ijfw team init is the concrete
command that writes .ijfw/team/, .ijfw/agents/, and Codex agent files.
Programmatic entry: createTeamAssembly(projectRoot, { brief, archetype, teamName }).
When brief is provided and contains explicit domain signal
(book/novel/chapter, marketing/campaign/launch,
research/paper/study, software/app/api, etc.) the brief score
outweighs filesystem-only detection. This is the wire that closes the
"Receive project brief from Discovery stage" flow below.
How It Works
- Receive project brief from Discovery stage (or ask for context)
- Infer one or more project archetypes and artifact types
- Identify the roles needed for creation, review, integration, and verification
- Generate portable agent markdown files with proper frontmatter
- Generate Codex custom-agent TOML when the Codex surface is present
- Generate the team charter and workflow manifest
- Present the proposed team and operating model for approval
- Save approved outputs to
.ijfw/agents/,.codex/agents/, and.ijfw/team/as applicable
Operating Outputs
Team Assembly 2.0 produces three coordinated surfaces:
.ijfw/agents/*.md-- portable human/platform-readable agent definitions.codex/agents/*.toml-- Codex custom agents generated from the same role contracts when Codex is installed orijfw codex sync-agentsis run.ijfw/team/charter.json-- team roster, role contracts, phase scope, owned artifacts, reviewed artifacts, conflict rules, handoff requirements, verification responsibilities.ijfw/team/workflow.json-- project work manifest: archetypes, artifacts, owners, dependencies, waves, review graph, verification commands or rubrics
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 · 394 lines · 43 tokens per session scan A b5d84a5f3c03
ijfw-team is a skill published in the GitHub repository FerroxLabs/ijfw (214 stars, last pushed 5d ago), licensed MIT. It adds 43 tokens to every session and 3,601 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-09-05.
Other skills, from other repositories
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
subagent-driven-development
A development workflow in which a fresh coding agent implements each independent task, another review checks that task, and a final review examines the complete set of changes.
adr
Create and manage Architecture Decision Records. Documents significant technical decisions with context, alternatives, and consequences. Also supports evaluate (assess proposals) and design (system design) modes.
deploy-checklist
Pre-deployment verification checklist. Generates customized checklists based on tech-stack with rollback triggers. Auto-invoked by /draft:upload.