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 AraneaDev/Knossos-MCP --skill knossosgit clone --depth 1 https://github.com/AraneaDev/Knossos-MCPWrote 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/araneadev/knossos-mcp/knossos)<a href="https://agentmods.dev/skills/araneadev/knossos-mcp/knossos"><img src="https://agentmods.dev/badge/skills/araneadev/knossos-mcp/knossos/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/araneadev/knossos-mcp/knossos"><img src="https://agentmods.dev/badge/skills/araneadev/knossos-mcp/knossos.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.00078 | $0.00790 |
| Opus 5 | $0.00039 | $0.00395 |
| Sonnet 5 | $0.00016 | $0.00158 |
| Haiku 4.5 | $0.00008 | $0.00079 |
Grade A, and why
knossos 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 yesterday.
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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Asking the graph instead of reading the tree
Knossos scans a repository once and answers structural questions from a graph where every fact points at a file and a line. The point is to stop re-deriving the same structure by reading the same files.
Route these questions to the graph
| About to | Ask instead |
|---|---|
| grep for callers of a symbol | list_usages, exact call sites with line numbers |
| guess what a change breaks | impact_analysis, dependants with confidence and evidence |
| read several files to trace a request path | explain_flow |
| decide where a new file belongs | suggest_location |
| eyeball a diff for architectural risk | review_diff |
| work out what a class is and what it touches | find_component, then inspect_component |
Every project-scoped tool needs a project_id. The session brief puts it in
context already. If it is not there, list_projects returns it.
Do not route these
Reaching for the graph here wastes a call and returns the wrong shape:
- Exact string or regex search, a config key, an error message, a TODO. Use grep.
- Reading a file you are about to edit. Edit needs the exact bytes, so use Read.
- Anything about runtime values or behaviour. The graph is static and never executes anything, so it cannot tell you what a variable holds.
- Confirming an edge labelled
probableorpossible. Those are leads to check in the source, not facts. - Anything structural while the session brief says
STALE,UNVERIFIED,NO GRAPHorNOT SCANNED. Runscan_projectfirst, or accept that the answer may describe a codebase that no longer exists.
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.
- yesterday First seen · 70 lines · 78 tokens per session scan A 28bb54844fc9
knossos is a skill published in the GitHub repository AraneaDev/Knossos-MCP (3 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 790 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-09-11.
Other skills, from other repositories
arch-optimize
A software architecture review workflow that scans a codebase for structural risks and measures code quality. It checks issues such as overly complex code, repeated knowledge, changes spreading across many files, circular dependencies, and distorted domain models.
Data Flow & State Ownership
Ensure designs define data flow, state ownership, consistency boundaries, and cross-boundary writes to prevent drift and incidents.
iac
Infrastructure as Code for .NET on Azure - defines, reviews, and troubleshoots Bicep and Terraform for .NET applications. Use when the user says "/iac", "infrastructure", "Bicep", "Terraform", "ARM template", "provision resources", "Azure resources", "deploy infra", "cloud setup", "new environment", or wants to…
incoherence-detector
Activated when: "check consistency", "find mismatches", "incoherence", "specs match code", "docs outdated", "sync check", "drift".
codemap
Generate and incrementally maintain an interactive architecture map plus a per-module code-quality audit (health scores 0-100, smell findings, lines-of-code, and a clickable dependency graph) for any codebase. Use when the user wants to visualize a project's functional modules, audit or score code quality, check…
refactor
Automated iterative code refactoring with swarm-orchestrated specialist agents including deep codebase discovery, confidence-scored code review, and security analysis. Use this skill when the user wants to improve existing code quality, clean up messy code, restructure, simplify, reduce tech debt, or perform…