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 agentmods add agents/gvastethecreator/codex-studio/issue-trackergit clone --depth 1 https://github.com/gvastethecreator/codex-studioWhat 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 | $0.00000 | $0.01020 |
| Opus 5 | $0.00000 | $0.00510 |
| Sonnet 5 | $0.00000 | $0.00204 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade A, and why
issue-tracker 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 2d 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.
Project tracker: GitHub plus local mirrors
GitHub Issues and the linked GitHub Project hold live work state. Local Markdown files hold synchronized briefs, decisions, evidence, and handoffs.
Identity
- Repository:
gvastethecreator/codex-studio - Project owner:
gvastethecreator - Project number:
8 - Project title:
Codex Studio - Project URL: https://github.com/users/gvastethecreator/projects/8
- Local root:
.scratch/codex-studio/
Authority
- GitHub owns open or closed state, assignees, comments, native dependencies, labels, and Project field values.
- Local files own expanded task context, decisions, proof, and offline handoff notes.
- Shared fields must match: title, category, triage state, execution state, source, dependencies, acceptance criteria, and outcome.
- Do not copy the full GitHub comment history into local files. Add durable decisions and proof to
## Sync log.
Local layout
- Spec:
.scratch/codex-studio/spec.md(PRD.mdremains compatible). - Ticket mirrors:
.scratch/codex-studio/issues/<NN>-<slug>.md. - Rejected requests:
.scratch/codex-studio/out-of-scope/<concept>.md. - Execution state:
.scratch/planning/. - Wayfinding mirrors:
.scratch/wayfinder/<effort-slug>/.
Each mirrored ticket starts with these fields:
# <NN>: <title>
GitHub issue: <url-or-pending>
GitHub project: https://github.com/users/gvastethecreator/projects/8
Sync: pending | synced | conflict
Last synced: <ISO-8601-or-never>
Remote updated: <ISO-8601-or-unknown>
Category: bug | enhancement
Status: needs-triage | needs-info | ready-for-agent | ready-for-human | wontfix
Project status: Todo | In Progress | Done
Execution: queued | active | blocked | finished
Type: AFK | HITL
Source: <spec path, issue URL, or conversation>
Blocked by: <GitHub issue numbers or None>
Sync protocol
- Read the Issue, the Project item, and the local mirror before a mutation.
- If both surfaces changed after
Last synced, setSync: conflictand stop. - Write the local draft with
Sync: pendingbefore remote creation. - Create or update the GitHub Issue. Use native parent and blocking relationships when they are available.
- Add the Issue to Project
8undergvastethecreator. - Set the Project
Statusfield toTodo,In Progress, orDone. - Update the local identifiers, shared fields, timestamps, and
Sync: synced. - If a step fails, record the failed step under
## Sync log. Retry from the stored Issue URL.
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.
- 2d ago First seen · 88 lines · 0 tokens per session scan A 18428dc04c94
issue-tracker is an agent published in the GitHub repository gvastethecreator/codex-studio (12 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,020 tokens. 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 agents, from other repositories
model-advisor
Model discovery and recommendation agent. Delegates here when the user needs help choosing a RunAPI model by modality, action, constraints, or pricing.
image-generator
Use this agent when the conversation context involves generating or editing images. This agent should be used proactively when image creation would help the user's task. It also covers named product and brand assets, which users rarely call "images": app icons, bot avatars, logos, favicons, hero images, banners…
review
Pre-PR code review against the project's gates and cross-cutting contracts — read-only, run before any external reviewer.
silence-composer
Tier 0 音乐家圣人 · 锚 凯奇 (John Cage).
wizard-designer
Agent "wizard-designer" from SuanFishXYY/suanfish-design-system, covering 🧙 wizard-designer · 流程设计师, 你的领地, 步进器的唯一形态：内联面包屑, 不可妥协的事 and 入场动效.
marketing-creative
You are a specialized Marketing Creative Specialist agent with expertise in generating high-converting marketing materials, advertisements, and social media content. Your role is to help marketers, growth teams, and founders create compelling visual content that drives engagement and conversions.