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 kimimgo/viznoir --skill oss-workflowgit clone --depth 1 https://github.com/kimimgo/viznoirWrote 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/kimimgo/viznoir/oss-workflow)<a href="https://agentmods.dev/skills/kimimgo/viznoir/oss-workflow"><img src="https://agentmods.dev/badge/skills/kimimgo/viznoir/oss-workflow.svg" alt="Measured on agentmods" 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.00062 | $0.00370 |
| Opus 5 | $0.00031 | $0.00185 |
| Sonnet 5 | $0.00012 | $0.00074 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
oss-workflow 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 8d 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.
What it actually says
OSS Workflow
1. Contributor Onboarding
- New issue/PR → label
good-first-issueif appropriate - Review with friendly, educational tone
- After merge → thank-you comment + mention in CHANGELOG
- Track contributors: Shirish-12105 (#11), himax12 (#7)
2. Release Management
- Check CHANGELOG.md for completeness
- Release Please auto-creates version bump PR on main push
- Merge Release Please PR → GitHub Release auto-published
- PyPI publish via
publish.yml(OIDC trusted publisher) - Update README badges if needed
- Note: PyPI Trusted Publisher must be configured at pypi.org
3. Issue Triage
- Categorize: bug / feature / question / showcase
- Assess reproducibility for bugs
- Label priority: P0 (critical) / P1 (important) / P2 (nice-to-have)
- Assign to milestone (v0.8.0, v0.9.0, backlog)
4. Showcase Curation
- New domain data →
inspect_data→cinematic_render - Add to README showcase gallery
- Datasets at
/mnt/dataset/viznoir-showcase/(4.1GB, 16 domains) - Connection: awesome-ai-cae list for viznoir exposure
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.
- 8d ago First seen · 37 lines · 62 tokens per session scan A 94900a8c8575
oss-workflow is a skill published in the GitHub repository kimimgo/viznoir (17 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 370 once invoked, about $0.0003 per session on Opus 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
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
github-cli
Default GitHub skill for the action agent. Use githubcli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shellrun/!gh. Run these with githubcli in the current agent turn.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…