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 mishahanin/heading-os --skill viraidgit clone --depth 1 https://github.com/mishahanin/heading-osWrote 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/mishahanin/heading-os/viraid)<a href="https://agentmods.dev/skills/mishahanin/heading-os/viraid"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os/viraid/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mishahanin/heading-os/viraid"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os/viraid.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 6 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00122 | $0.02125 |
| Opus 5 | $0.00061 | $0.01063 |
| Sonnet 5 | $0.00024 | $0.00425 |
| Haiku 4.5 | $0.00012 | $0.00213 |
Grade A, and why
viraid 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 5d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Viraid -- Virtual Assistant for Telegram Task Capture
Reads new messages from the VIRAID Telegram channel and categorizes them. The channel defaults to M's VIRAID; set VIRAID_CHANNEL_NAME in .env to use your own. It then enriches with workspace context (CRM, calendar, pipeline), proposes structured actions, and executes after Misha's approval. Nothing falls through the cracks.
State Files
State lives in the DATA overlay, never the engine. Resolve the directory once at the start of a run (from the engine root):
VIRAID_DIR="$(python3 -c "import sys; sys.path.insert(0,'.'); from scripts.utils.workspace import get_outputs_dir; print(get_outputs_dir())")/operations/viraid"
Then state.json = $VIRAID_DIR/state.json, tasks.md = $VIRAID_DIR/tasks.md. Read and write
only there. Never write viraid state into the engine tree: .heading-os/outputs/... must not be
created. A bare relative path resolves against the engine git root, where outputs/ does not exist.
Channel name is configurable. The Telegram channel Viraid reads is NOT hardcoded. Resolve it
once at run start; it comes from the VIRAID_CHANNEL_NAME env var (in .env), defaulting to
M's VIRAID when unset:
VIRAID_CH="$(python3 -c "import sys; sys.path.insert(0,'.'); from scripts.utils.workspace import load_env, get_workspace_root; load_env(get_workspace_root()); import os; print(os.environ.get('VIRAID_CHANNEL_NAME', 'M'+chr(39)+'s VIRAID'))")"
Use "$VIRAID_CH" wherever a fetch/delete command names the channel. The canonical fetch commands
below inline this resolver so they work in a single shell call.
- Ledger:
$VIRAID_DIR/state.json-- single source of truth for all processed messages - Tasks:
$VIRAID_DIR/tasks.md-- active and completed action items
Action Router
| Invocation | Action |
|---|---|
/viraid (no args) |
Process new messages (Steps 1-9) |
/viraid sweep |
Triage active tasks (see Sweep section) |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 158 lines · 122 tokens per session scan A 8045cc0cd1c3
viraid is a skill published in the GitHub repository mishahanin/heading-os (11 stars, last pushed today), licensed Apache-2.0. It adds 122 tokens to every session and 2,125 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
shogun-model-switch
A live-switching tool for changing which command-line AI agent, model, and reasoning mode is running. It updates settings, restarts the agent, and refreshes the displayed session information.
toolbox
Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing…
devops-expert
Expert-level DevOps practices, culture, automation, and continuous delivery. Use when the user mentions CI/CD, automation, infrastructure, or culture, or when the task involves DevOps Culture or Culture & Process.
file-collect-sort-action
Erkennt Nutzeraufträge der Form "hole aus einem Ordner immer bestimmte Dateien und sammle sie an einem Ziel" und richtet dafür das Modul file-collect-sort-action (CLI fcsa) ein — ein konfigurationsgetriebener Agent, der Ordner scannt, Dateien per Schablone kategorisiert und gestufte Aktionen anwendet…
ibrahim-daily-briefing
Generate Ibrahim's daily briefing — new leads, upcoming calls, pending follow-ups, system health, and one strategic question. Delivered to Telegram.
wecomcli-todo
A tool for managing to-do items in WeCom, the workplace messaging and collaboration app used by many Chinese companies. It handles existing WeCom tasks and their titles, descriptions, people, status, and deadlines.