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 clonegit 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/clone)<a href="https://agentmods.dev/skills/o-samoilov/quasar-graph/clone"><img src="https://agentmods.dev/badge/skills/o-samoilov/quasar-graph/clone.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.00061 | $0.02199 |
| Opus 5 | $0.00030 | $0.01099 |
| Sonnet 5 | $0.00012 | $0.00440 |
| Haiku 4.5 | $0.00006 | $0.00220 |
Grade A, and why
clone 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/quasar-graph:clone
Clone the project/service repositories of a backend graph onto the local machine, recreating each project at its recorded relative path under a user-chosen base directory.
This is the inverse of scan. It is stateless — it does not write to .quasar-graph/; on disk it changes only the chosen base directory (where it clones repos) and the saved base_dir in ~/.quasar-graph/config.json. It requires the quasar-graph MCP server (the graph lives on the backend — there is no offline mode).
Inputs (asked in this order)
- Backend project + graph — chosen interactively in Phase 0.
base_dir— absolute local root to clone into. Default: the savedbase_dirfrom~/.quasar-graph/config.jsonif present, else~/Projects(resolve~to$HOME). Asked at the start of Phase 1; the confirmed answer is saved back to that config.protocol—ssh(default) orhttps. Asked at the start of Phase 1.install— install dependencies after cloning?Yes/No. Default No. A single prompt that applies to every cloned/updated project. Asked at the start of Phase 1.
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, and the login retry flow.
Fixed choices in this skill that always use a selection prompt: protocol (ssh / https), install (yes / no), new-vs-existing graph (if you offer it), and the final "confirm before cloning" gate — recommended/default option first. An empty backend list means report and stop (Phase 0 handles the empty-projects case); free-form inputs (the base_dir path) stay plain text.
Phase 0 — Select project & graph
- Confirm the
quasar-graphMCP tools are available. If not, report:Clone needs the quasar-graph MCP server (the graph lives on the backend). Enable it and retry.Then stop. - Authentication. On a
Not authenticated with the quasar-graph backendfailure, run the login retry flow from the conventions file. If it still fails, stop (clone has no offline mode). - Call
list_workspacesandlist_projects. Ask which project to clone from using the selection UI rules (picker if ≤ 4, else numbered table; incl. workspace labeling). If empty, report there are no projects on the backend and stop. Captureproject_id. - Call
list_graphswithproject_id. If the list is empty, report that this project has no graphs on the backend (suggest running/quasar-graph:scanfirst) and stop. Otherwise ask which graph to clone the same way (picker if ≤ 4, else numbered table); showname / nodes_count / scanned_atper option. Capturegraph_id.
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 · 84 lines · 61 tokens per session scan A 0dec34dd442d
clone is a skill published in the GitHub repository o-samoilov/quasar-graph (3 stars, last pushed 25d ago), licensed MIT. It adds 61 tokens to every session and 2,199 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-31.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".