Share Config
Developmentshare-configShare Config is an Agent Skill for development published in the hashgraph-online/awesome-codex-plugins repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Promote local config to a shared team config that can be committed to git.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/hashgraph-online/awesome-codex-plugins/blob/HEAD/plugins/yimwoo/codex-agenteam/skills/share-config/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/share-config, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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"
Notes
- The team config becomes the source of truth for pipeline, stages, gates, roles, and isolation.
- Personal overrides in
.agenteam/config.yamlcan only changemodel,reasoning_effort,system_instructions(append),nickname_candidates,mcp_servers, andskills_config. - The team can widen personal overrides with
allow_personal_overridein the team config.