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/open-software-network/os-clovy/issue-trackergit clone --depth 1 https://github.com/open-software-network/os-clovyWhat 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.00770 |
| Opus 5 | $0.00000 | $0.00385 |
| Sonnet 5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue tracker: os-platform
Issues for this repo live on the Open Software platform (os-platform), org
june — NOT GitHub Issues. GitHub Issues exist on the repo but are a
legacy/watchdog surface, not the triage queue.
All reads go through the vendored os-platform skill
(.agents/skills/os-platform/). Run its script from that directory; it needs
OS_PLATFORM_API_KEY in the environment (never paste keys into chat).
Defaults (org june, limit 20) come from os-platform.json at the repo root.
Read conventions
- List issues:
python3 scripts/os_platform.py issues list june --status todo(filters:--status todo,in_progress,in_review,completed,cancelled,--labels,--assignee,--priority,--project,--q) - Search:
python3 scripts/os_platform.py issues search june "<query>" - Read an issue:
python3 scripts/os_platform.py issues show june <number>(comments:comments list issue june <number>) - Take an issue (todo → in_progress, assigns you):
python3 scripts/os_platform.py issues take june <number>— confirm with the user before passing--yes.
Write conventions
The os-platform script owns routine workflow writes. Run it from
.agents/skills/os-platform/ and verify each write with a read before any
fan-out:
- Create an issue:
python3 scripts/os_platform.py issues create june --title "..." --body "..."(optional:--type feature|bug|other,--priority low|med|high). - Assign yourself:
python3 scripts/os_platform.py issues assign june <number>. - Change status:
python3 scripts/os_platform.py issues status june <number> <status>where status istodo|in_progress|in_review|completed|cancelled. - Add a comment:
python3 scripts/os_platform.py comments add june <number> --body "...".
issues take remains the confirmed shortcut that assigns an unassigned todo
Issue to the authenticated user and moves it to in_progress.
Issue body edits are still append-only and are not exposed by
os_platform.py: fetch the full current body first, append, and never
overwrite. The direct endpoint remains
PATCH /v1/orgs/june/bounties/{number} with the combined body as
{"body_markdown": "..."}. Prefer os-task-prep/scripts/enrich_issue.py for
diagnosis notes. Other mutations not owned by the script, such as body or
label updates, keep the direct API probe-then-verify discipline. Confirm any
fan-out mutation on one Issue before applying it to many — this is a shared
production tracker.
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 · 72 lines · 0 tokens per session scan A 8588dbc9da28
issue-tracker is an agent published in the GitHub repository open-software-network/os-clovy (357 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 770 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
demo-agents
We need a steady flow of demo videos — X/Twitter, Reddit, YouTube Shorts, blog posts, App Store-style screen recordings — and we'd like to scale that without scheduling Daniel to record every clip by hand. This doc maps the content-creation agent landscape, names the gap between "synthetic video hype" and "scripted…
qa-agents
Every quarter someone pitches an "AI does QA" tool. Most are web-first or mobile-first. MacParakeet is a menu-bar macOS app with a non-activating KeylessPanel overlay, global dictation hotkeys, and TCC-gated microphone/screen-recording flows. The general AI-QA frontier doesn't speak our shape yet. This doc tracks…
flow-verifier
Runs the VZT Flow end-to-end verification ladder (build, tests, TTS-transcribe checks, clean-test latency, paste-test, daemon socket checks, overlay states) and reports real measured numbers — never estimates. Use before claiming a change works, before a release, or when asked to verify VZT Flow.
flow-feature-builder
Implements VZT Flow features observing this repo's boundaries — additive edits, the gotcha list from CLAUDE.md, pull-rebase discipline in a shared worktree, never touching the user's running daily-driver app without relaunching it. Use for routine feature/bugfix work in this repo.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
ai-systems-architect
Use as the cross-cutting AI/systems DESIGN authority to decide WHERE a seam goes across the Rust core, Angular FE, and brain — provider/model abstraction, agentic tool-use loop bounds, tool/ACI design, the egress-consent-redaction-ledger firewall, routing, context assembly, a new ingest source or consumption surface.…