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 juliakrivchikova/AccordAgents-desktop-app --skill accordgit clone --depth 1 https://github.com/juliakrivchikova/AccordAgents-desktop-appWrote 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/juliakrivchikova/accordagents-desktop-app/accord)<a href="https://agentmods.dev/skills/juliakrivchikova/accordagents-desktop-app/accord"><img src="https://agentmods.dev/badge/skills/juliakrivchikova/accordagents-desktop-app/accord/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/juliakrivchikova/accordagents-desktop-app/accord"><img src="https://agentmods.dev/badge/skills/juliakrivchikova/accordagents-desktop-app/accord.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00074 | $0.03038 |
| Opus 5 | $0.00037 | $0.01519 |
| Sonnet 5 | $0.00015 | $0.00608 |
| Haiku 4.5 | $0.00007 | $0.00304 |
Grade A, and why
accord 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 12d 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accord
Lead a bounded, skeptical discussion among current chat participants that ends in one agreed resolution, captured as a signable artifact.
Use only when User explicitly wants an accord: multi-participant consensus, cross-checking, combined findings, or a plan/decision approved by every involved participant. Not for an ordinary answer, a normal review, a "double-check", or a "what do you think". When unsure whether User wants multiple participants, ask first.
Core Rules — independent drafts first; approval = current signatures
Before anyone sees another participant's proposal, every Accord author must submit one frozen, attributable draft to the same collecting artifact. You (the facilitator) submit first, before requesting participants. Each selected participant submits independently. Draft bodies are not chat content: User can always read every draft; you can read every participant draft because each participant explicitly includes you in its audience; peers cannot read one another's drafts. Public chat may say that a draft was submitted, but must never contain draft content, snippets, readers, or summaries.
After all required drafts are frozen, publish canonical v1 by synthesizing them
and recording every required current draft as a considered source. Draft
authorship is provenance, never approval and never a signature. The published
resolution's requiredSigners are you and every selected participant. Consensus
is reached only when
approval.state === "approved" — every required signer has signed the current
version — you have signed it too, and no selected participant has an open
objection against that version. Approval is signature identity on the current
version, never reply prose: a reply can raise a concern but is not a second
approval step, and a concern raised in a reply without signing is a non-approval.
Signature/version semantics (stated once): app_artifact_revise creates a new
version that starts unsigned; signatures on earlier versions stay in history
but no longer count. So any edit invalidates stale approvals and forces a fresh
sign round — the artifact tracks "who approved the current version" for you.
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.
- 12d ago First seen · 260 lines · 74 tokens per session scan A d2fefbf12c17
accord is a skill published in the GitHub repository juliakrivchikova/AccordAgents-desktop-app (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 74 tokens to every session and 3,038 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…