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 o-samoilov/quasar-graph --skill contextgit clone --depth 1 https://github.com/o-samoilov/quasar-graphWrote 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/o-samoilov/quasar-graph/context)<a href="https://agentmods.dev/skills/o-samoilov/quasar-graph/context"><img src="https://agentmods.dev/badge/skills/o-samoilov/quasar-graph/context.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.00159 | $0.02183 |
| Opus 5 | $0.00079 | $0.01092 |
| Sonnet 5 | $0.00032 | $0.00437 |
| Haiku 4.5 | $0.00016 | $0.00218 |
Grade A, and why
context 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 7d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/quasar-graph:context
Bind the project you are working in to its node in a backend graph, load its connections into the session, and keep them available for the rest of the work: structural questions are answered from the graph, and — only after explicit confirmation — the agent reads the source code of neighbor projects.
This is the in-session counterpart to research: research is a standalone Q&A loop over a manually picked project + graph; context binds to the current project automatically and then stays in the background of normal work. It is read-only w.r.t. the graph — it never calls build_graph / push_graph / write_node_manifests / create_graph / pull_graph and writes nothing under .quasar-graph/. The only things it may change on disk are cloning confirmed missing neighbor repos into base_dir (Phase 2) and the saved keys in ~/.quasar-graph/config.json; the binding cache in ~/.quasar-graph/cache/bindings.json is maintained by the bind_context tool it calls. It requires the quasar-graph MCP server (the graph lives on the backend — there is no offline mode).
Optional argument: /quasar-graph:context <path> binds that directory instead of the current working directory. Everything below calls it the target directory.
Conventions
Read references/conventions.md at the quasar-graph plugin root before acting. It defines the action vocabulary this skill is written in (dispatch a sub-agent, load a skill, selection prompt, …) with its per-harness degradations, the selection UI rules, the login retry flow, and the repo identity & binding cache rules.
In this skill the selection UI covers candidate nodes in Phase 0 (from bind_context's candidates list on status: ambiguous; label = node name + graph name, description = the node's own description) and every look-into-neighbor confirmation in Phase 2; free-form inputs (the base_dir path) stay plain text.
Phase 0 — Bind
Goal: resolve which graph node is the current project and load that graph into context (NOT to disk).
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.
- 7d ago First seen · 58 lines · 159 tokens per session scan A 1f5517a60689
context is a skill published in the GitHub repository o-samoilov/quasar-graph (3 stars, last pushed 25d ago), licensed MIT. It adds 159 tokens to every session and 2,183 once invoked, about $0.0008 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-31.
Other skills, from other repositories
mempalace-task
Create, hand off, claim, execute, and close agent tasks through the MemPalace logstream. Use when the user wants to delegate work, prepare a ready-to-paste task for another agent, receive a MemPalace task id, or explicitly launch a supported headless agent in controlled mode.
neat-freak
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…
gsd-mempalace-capture
File a phase artifact into MemPalace; mirror decision facts into its temporal KG.
md-hive-sync
Munder Difflin hive sync — runs the start-of-task hive protocol steps: reads memory.md, checks inbox/ for new messages, and reminds you to record durable facts in memory.md and write coordination files before ending. Use when asked to "sync with the hive", "check my inbox", "hive status", or "hive sync". Proactively…
commonly
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…
github-ops
GitHub CLI for issues, PRs, code search, CI logs, releases, and API queries. Requires gh CLI and auth.