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 cdskill/qalma --skill qalma-docs-syncgit clone --depth 1 https://github.com/cdskill/qalmaWrote 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/cdskill/qalma/qalma-docs-sync)<a href="https://agentmods.dev/skills/cdskill/qalma/qalma-docs-sync"><img src="https://agentmods.dev/badge/skills/cdskill/qalma/qalma-docs-sync/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/cdskill/qalma/qalma-docs-sync"><img src="https://agentmods.dev/badge/skills/cdskill/qalma/qalma-docs-sync.svg" alt="Reviewed on agentmods" width="80" 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.00079 | $0.00773 |
| Opus 5.5 | $0.00032 | $0.00309 |
| Sonnet 5.5 | $0.00016 | $0.00155 |
| Haiku 4.5 | $0.00008 | $0.00077 |
Grade A, and why
qalma-docs-sync 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 1mo 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Qalma Docs Sync
Keep public documentation in lockstep with Qalma's headless plugin surface. Run this after any plugin or public editor capability changes.
Sync Checklist
- Inspect the changed plugin exports in
libs/editor/src/index.tsand the implementation underlibs/editor/src/lib/plugins. - Update
libs/editor/README.md:- Add, rename, or remove the plugin in the Available plugins table.
- Include consumer-facing command names.
- Mention public queries, events, kits, or configuration where they affect consumer integration.
- Update
apps/docs/src/app/docs/docs-nav.ts:- Add a sidenav entry for new user-facing plugin documentation.
- Place plugins by product area: formatting, document structure, media and links, productivity, layout, or guides.
- Update or create markdown pages in
apps/docs/src/content/docs:- Use frontmatter with
titleanddescription. - Explain selection in
plugins, public commands, public queries, public options/defaults, shortcuts/events, and consumer-owned UI responsibilities. - Prefer small complete Angular examples over internal implementation notes.
- Use frontmatter with
- If the live docs playground demonstrates the feature, update
apps/docs/src/app/playgroundthrough the public@qalma/editorAPI only. - If the sandbox demonstrates the feature, keep
apps/sandboxand docs playground behavior conceptually aligned unless the docs intentionally use a smaller example. - Update repository guidance when the workflow changes:
AGENTS.mdfor durable agent instructions..agents/skills/qalma-plugin-developmentif plugin definition-of-done or workflow expectations change.
- Update
plugins/qalma/skills/qalmawhen public agent guidance becomes stale:- Add, rename, or remove public plugin names, commands, queries, and options.
- Keep integration examples aligned with current public imports.
- Keep contributor workflow guidance aligned with repository expectations.
- Validate the changed surface with the narrowest useful checks:
pnpm exec tsc -p libs/editor/tsconfig.lib.json --noEmitpnpm exec tsc -p apps/docs/tsconfig.json --noEmitpnpm nx build docs- Relevant lint targets, noting unrelated existing failures separately.
What ships with it
1 file 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.
- 1mo ago First seen · 63 lines · 79 tokens per session scan A ef15c0e19424
qalma-docs-sync is a skill published in the GitHub repository cdskill/qalma (10 stars, last pushed 2d ago), licensed MIT. It adds 79 tokens to every session and 773 once invoked, about $0.0003 per session on Opus 5.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
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
update-skills
Create or update repository skills and instructions when major learnings are discovered during a session. Use when the user says "learn!", when a significant pattern or pitfall is identified, or when reusable domain knowledge should be captured for future sessions.
sync
Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.
generate-run-commands
Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.
create-canvas
Create a Copilot extension canvas at user, workspace, or plugin scope.
create-skill
Create a reusable skill (SKILL.md) that packages a workflow.