Agent skill · Audited from source
role-creator
skill · am-will/codex-skillsLicence not declaredAudited 31 Oct 2026 · source 31eb89d791f0
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 31eb89d791f0 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Create and update Codex custom agents using standalone custom-agent TOML files.
Cite
Cite this page
ModelsAtlas. “role-creator (am-will/codex-skills)”. Retrieved 31 Oct 2026. https://modelsatlas.com/skills/am-will/role-creator
Trust audit
Audit 0.4.1 · source read 31 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 16,667 of 17,602 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 1 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | PASS | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass, no license.
Findings (1)
LOWInventory / provenanceinv.no_license
- Why
- no LICENSE file and no repo licence
- Fix
- add a licence
Audit 0.4.1 · source sha 31eb89d791f0 · 31 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisheram-will GitHub userOwner of the repository this skill is read from
- Source folderam-will/codex-skills/skills/role-creatorThe exact folder we audited
- LicenceNot declaredAs the repository states it
- Commit pinned for this verdict31eb89d791f0A new audit runs when the source changes
- Repository statusNot archivedLast push 108 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Create and update Codex custom agents using standalone custom-agent TOML files.
---
name: role-creator
description: Create and update Codex custom agents using standalone custom-agent TOML files.
---
# Role Creator
## Overview
Use this skill to author, update, or troubleshoot custom Codex agents as standalone TOML files.
Current behavior:
- Each custom agent is defined by one file:
- Global: `~/.codex/agents/<agent-name>.toml`
- Project: `<project>/.codex/agents/<agent-name>.toml`
- The agent file is the role source of truth.
- `~/.codex/config.toml` is only for global/runtime settings (for example `[agents]` thread limits), not per-role registration.
## Non-Negotiable Inputs
Step 1 is required before writing files:
- `name` (role identifier used by `agent_type`)
- `description` (short, human-readable purpose)
- `developer_instructions`
- `model` (recommend `gpt-5.3-codex` unless requested)
- `model_reasoning_effort` (`none|minimal|low|medium|high|xhigh`)
- role scope (`global` or `project`)
- output TOML path (canonical absolute path preferred)
- whether to include `nickname_candidates` and exact values
Execution rule:
- Do not infer required values.
- Do not write until required inputs are explicitly confirmed.
## Role file contract (current)
From Codex custom agent docs (`/codex/subagents`):
- Required keys: `name`, `description`, `developer_instructions`.
- Optional keys: `nickname_candidates`, `model`, `model_reasoning_effort`, `sandbox_mode`, `web_search`, `mcp_servers`, `skills.config`, etc.
- `name` is the spawn identifier and source of truth.
- `description` + `developer_instructions` define behavior and usage boundaries.
- `nickname_candidates` is optional and used only for display.
`nickname_candidates` requirements:
- Must be a non-empty list of unique values when present.
- Allowed characters: ASCII letters, digits, spaces, hyphens, underscores.
## Default policy for optional settings
- Do not add sandboxing/MCP/web-search/model extras unless requested.
- Keep generated files minimal by default.
- If the user says "inherit defaults", omit optional keys instead of setting explicit values.
## Workflow
1. Collect and confirm required inputs.
2. Resolve output path:
- `global` → `~/.codex/agents/<name>.toml`
- `project` → `<project>/.codex/agents/<name>.toml`
3. Create or update the file directly with required keys.
4. Validate TOML parse and required keys.
5. Return a ready-to-run example call:
```json
{"agent_type":"<name>","message":"<task>"}
```
## Commands
```bash
# 1) Write a standalone custom-agent file
/home/willr/Applications/skills/skills/role-creator/scripts/write_role_config.sh \
--output ~/.codex/agents/reviewer.toml \
--role-name reviewer \
--description "PR reviewer focused on correctness, security, and risk." \
--model gpt-5.4 \
--reasoning high \
--developer-instructions "Review code like an owner. Lead with concrete findings and residual risks."
# Optional: include nickname candidates for display
/home/willr/Applications/skills/skills/role-creator/scripts/write_role_config.sh \
--output ~/.codex/agents/reviewer.toml \
--role-name reviewer \
--description "PR reviewer focused on correctness, security, and risk." \
--model gpt-5.4 \
--reasoning high \
--developer-instructions "Review code like an owner. Lead with concrete findings and residual risks." \
--nickname-candidates "Atlas,Delta,Echo" \
--sandbox-mode read-only \
--web-search disabled
```
## Guardrails
- If runtime returns `unknown agent_type`, verify the active scope and confirm the file exists at the expected path.
- Check syntax first with `tomlq` or `tomlq -C`.
- Keep role instructions operational and narrowly scoped to avoid drift.
## References
- Codex subagents docs: `https://developers.openai.com/codex/subagents`
- Display nicknames: `https://developers.openai.com/codex/subagents#display-nicknames`
- Reusable templates: `templates/`Excerpt, first 3,878 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 31eb89d
git clone https://github.com/am-will/codex-skills git -C codex-skills checkout 31eb89d791f0
The author documents no install command, so this uses the repository directly. Our verdict covers commit 31eb89d791f0 only.
Works in which agents?
What its own text says, not a test
| Agent | Status | More |
|---|---|---|
| Codex | Mentioned in its text, not tested | Skills for Codex · About Codex |
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
31eb89d791f0
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/am-will/role-creator/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
obra/superpowers
Use when creating new skills, editing existing skills, or verifying skills work before deployment
mattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Add this badge to your README
[](https://modelsatlas.com/skills/am-will/role-creator/)
<a href="https://modelsatlas.com/skills/am-will/role-creator/"><img src="https://modelsatlas.com/skills/am-will/role-creator/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about role-creator
Is role-creator safe to install?
What can role-creator access on my machine?
Which assistants does role-creator work with?
How current is this page?
Sources
- github.com/am-will/codex-skills/tree/main/skills/role-creator — the audited source at commit 31eb89d791f0 and every finding aboveObserved · 31 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- Is role-creator safe to install?
- What can role-creator access on my machine?
- Which assistants does role-creator work with?