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 agentmods add skills/cirwel/unitares/knowledge-graphnpx skills add cirwel/unitares --skill knowledge-graphgit clone --depth 1 https://github.com/cirwel/unitaresWhat 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 | $0.00037 | $0.01903 |
| Opus 5 | $0.00018 | $0.00951 |
| Sonnet 5 | $0.00007 | $0.00381 |
| Haiku 4.5 | $0.00004 | $0.00190 |
Grade A, and why
knowledge-graph 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 2d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Graph
What It Is
The knowledge graph is shared institutional memory across all agents. It is backed by PostgreSQL — full-text search is the canonical default backend, with Apache AGE as an optional graph backend (UNITARES_KNOWLEDGE_BACKEND=age). Every agent can search, contribute, and update entries. Discoveries persist across sessions and are available to all agents in the system.
Search Before Creating
Always search before adding new entries:
knowledge(
action: "search",
query: "description of what you're looking for",
tags: ["relevant", "tags"],
limit: 10
)
search_shared_memory(query=...) is the discoverable workflow alias for this
same read path. Use either it or the unified router; duplicate entries fragment
knowledge and make search less effective.
You may omit query entirely when filtering by tags, type, severity, dates, or
status. A supplied-but-blank query is rejected so a caller mistake cannot turn
into an accidental broad scan. Omit include_details to let the server expand a
small result set automatically; pass include_details=false when summaries only
are intentional.
Quick Contribution
For low-friction contributions, use the unified note action:
knowledge(
action: "note",
summary: "What you discovered or observed",
tags: ["domain", "type", "context"]
)
Notes are automatically shared with all agents. Use this when you find something useful, spot a bug, or have an insight that others should know about. leave_note() is also supported as a lower-friction entry point to the same handler.
For a structured discovery, prefer the dedicated workflow alias:
store_finding(
summary: "What was found",
discovery_type: "bug_found",
details: "Evidence and impact",
tags: ["domain", "component"]
)
Use update_finding(discovery_id=..., ...) to revise or close it. These aliases
route to knowledge(action="store") and knowledge(action="update"); they do
not create a second store.
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.
- 2d ago First seen · 189 lines · 37 tokens per session scan A 33c39bb7ec7f
knowledge-graph is a skill published in the GitHub repository cirwel/unitares (4 stars, last pushed 2d ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,903 once invoked, about $0.0002 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
adk-unit-design
Writes an as-built architecture document for one ADK code unit — purpose, execution flow, data flow, cross-class dependencies, extension points, and the parts that must not change — to docs/design/{topic}/{unit}/index.md. It describes the code as implemented, not a proposed design, and its reader is a developer about…
achieving-cmmc-level-2-compliance
Prepare a defense-contractor environment for CMMC Level 2 certification: scope CUI and FCI, implement the 110 NIST SP 800-171 Rev 2 security requirements across 14 families, compute the SPRS score with the DoD Assessment Methodology, manage a compliant POA&M, and ready the organization for a C3PAO assessment. Use when…
adk-setup
Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test run. Runs only when explicitly requested, never on its own. Use when asked to set up, bootstrap, or repair a development…
create-custom-grader
Use when converting an existing benchmark, rubric, verifier, task YAML/JSON, or domain check into SkillEvaluator BYOG/BYOT custom evaluation.
anthropic_administrator-automation
Automate Anthropic Admin tasks via Rube MCP (Composio): API keys, usage, workspaces, and organization management. Always search tools first for current schemas.
ai-ml-api-automation
Automate AI ML API tasks via Rube MCP (Composio). Always search tools first for current schemas.