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 yimwoo/codex-agenteam --skill share-configgit clone --depth 1 https://github.com/yimwoo/codex-agenteamWrote 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/yimwoo/codex-agenteam/share-config)<a href="https://agentmods.dev/skills/yimwoo/codex-agenteam/share-config"><img src="https://agentmods.dev/badge/skills/yimwoo/codex-agenteam/share-config/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/yimwoo/codex-agenteam/share-config"><img src="https://agentmods.dev/badge/skills/yimwoo/codex-agenteam/share-config.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.00019 | $0.00613 |
| Opus 5.5 | $0.00008 | $0.00245 |
| Sonnet 5.5 | $0.00004 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
share-config 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgenTeam Share Config
Create a shared team config from your local config so collaborators can use the same pipeline, roles, and settings.
Process
1. Check Prerequisites
Verify .agenteam/config.yaml (or legacy agenteam.yaml) exists.
If not, tell the user: "No local config found. Run @ATeam init first."
2. Check for Existing Team Config
If .agenteam.team/config.yaml already exists:
- Tell the user: "Team config already exists at
.agenteam.team/config.yaml. Edit it directly to change team settings." - Stop. Do not overwrite.
3. Load and Strip Personal Fields
Load the current config. Strip ALL personal-allowlist fields from every role:
model(personal preference)reasoning_effort(personal preference)system_instructions(may contain personal addenda)nickname_candidates(personal display preference)mcp_servers(local/private tool wiring)skills_config(local/private skill wiring)
These fields are stripped because they should not become team policy.
The user can review and re-add team-relevant instructions manually.
Stripping model intentionally restores platform default inheritance for
collaborators and avoids sharing a pin that may be unavailable in their Codex
catalog.
4. Normalize Version
If version is not "2", set it to "2".
5. Write Team Config
mkdir -p .agenteam.team
Write the stripped config to .agenteam.team/config.yaml.
6. Summary
Print:
Team config created at .agenteam.team/config.yaml
What was stripped (personal-only fields):
- roles.*.model
- roles.*.reasoning_effort
- roles.*.system_instructions
- roles.*.nickname_candidates
- roles.*.mcp_servers
- roles.*.skills_config
Review it before committing. To customize:
- Team settings: edit .agenteam.team/config.yaml (tracked in git)
- Personal overrides: create .agenteam/config.yaml (gitignored)
Next steps:
git add .agenteam.team/
git commit -m "Add shared AgenTeam team config"
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 · 88 lines · 19 tokens per session scan A cdc9d546a697
share-config is a skill published in the GitHub repository yimwoo/codex-agenteam (14 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 613 once invoked, about $0.0001 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-30.
Other skills, from other repositories
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
github
Interact with GitHub (issues, PRs, repos, releases) using the gh CLI. Use when asked to read or write GitHub state — open an issue, fetch PR diff, comment, list runs, etc.
working-in-turns
Keep each turn bounded, checkpointed, and reviewable.
major-version-mode
Context for working on the next AI SDK major release. Only use when explicitly invoked by the user (e.g. via '/major-version-mode'). Do NOT trigger autonomously based on task content.
gear
Managing dependencies, CI/CD, advanced GitHub Actions workflows, containers, secrets, and operational config. Use for build, workflow, or environment work.
launch
Planning releases and reporting delivery work from GitHub PR history. Use when versioning, CHANGELOGs, rollout or rollback plans, engineering metrics, retrospectives, or stakeholder reports are needed.