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 Vladick-Pick/business-ontology --skill system-analysisgit clone --depth 1 https://github.com/Vladick-Pick/business-ontologyWrote 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/vladick-pick/business-ontology/system-analysis)<a href="https://agentmods.dev/skills/vladick-pick/business-ontology/system-analysis"><img src="https://agentmods.dev/badge/skills/vladick-pick/business-ontology/system-analysis/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/vladick-pick/business-ontology/system-analysis"><img src="https://agentmods.dev/badge/skills/vladick-pick/business-ontology/system-analysis.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.00035 | $0.01232 |
| Opus 5 | $0.00017 | $0.00616 |
| Sonnet 5 | $0.00007 | $0.00246 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
system-analysis 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System analysis projection
Use this skill before invoking a systems-thinking tool over the company model. It prepares the slice of accepted ontology that the tool needs and prevents the tool from guessing a system from loose prose.
When to use
Use when the user asks to analyze the company model with:
- causal-loop or stock-flow thinking;
- Theory of Constraints;
- leverage-point analysis;
- TRIZ contradiction solving;
- why-tree/root-cause analysis.
Do not use this skill for standalone brainstorming that has no accepted ontology behind it.
Inputs
Read:
- the accepted model slice relevant to the problem;
agent-os/SYSTEM_ANALYSIS.md;specs/SYSTEM-ANALYSIS-SPEC.md;- source and evidence ids for the selected model slice;
- open drift and unknowns that could affect the analysis.
Projection shape
Prepare a bounded projection with kind: systemAnalysisProjection.
Use runtime.context_projection.build_system_analysis_projection when running
inside this package, and validate the shape against
schemas/system-analysis-projection.schema.json when possible.
The projection carries:
objective: measurable target or decision question;analysisIntent: downstream analysis intent, such asconstraint-finder,why-tree,triz,stock-flow, orleverage-finder;modelIds: accepted objects, states, workflows, metrics, and decisions;definitions: short accepted definitions with source ids;workflow: participants, steps, transitions, exceptions, and metrics;constraints: accepted bottlenecks, rules, policies, or source-of-truth limits;delays: known waiting time, review time, handoff time, feedback delay;metrics: formula, owner, source of truth, current value if available;drift: open model-vs-reality gaps;unknowns: missing fields that block the selected systems skill;evidenceQuality: review risk, evidence mode, source adequacy, and SLA band;competencyQuestions: questions this slice is supposed to answer;sourceSummary: source ids, evidence ids, review package ids, and source event ids.
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 · 157 lines · 35 tokens per session scan A d55d8699acd7
system-analysis is a skill published in the GitHub repository Vladick-Pick/business-ontology (2 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 1,232 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
graph-mutation-plan
Cookbook for composing an applygraphmutations plan — stable entitykey patterns, the canonical label/edge vocabulary, evidence/invalidation/confidence discipline, and a worked example. Load this when building a non-trivial mutation plan.
open-ontologies
AI-native ontology engineering using 50+ MCP tools backed by an in-memory Oxigraph triple store. Build, validate, query, and govern RDF/OWL ontologies with a generate-validate-iterate loop. Use when building ontologies, knowledge graphs, RDF data, SPARQL queries, BORO/4D modeling, SHACL validation, clinical…
Rare Disease Skills Index
Skills for rare disease case support: ontology-first normalization/retrieval and the clinical genetics consult report format contract (structure + theme). Load the relevant skill file when performing the matching task.
objectstack-platform
Bootstrap, configure, extend, and operate ObjectStack runtimes. Covers project setup (defineStack, drivers, scaffolding), declaring platform capabilities (requires: — which service plugins boot), plugin and service development (PluginContext, DI, kernel hooks like kernel:ready), and operations (CLI commands…
objectstack-automation
Design ObjectStack automation — Flows (visual logic), Triggers, Approvals, state machines, and the jobs (defineJob) / webhooks (defineWebhook) stack collections. Use when the user is adding .flow.ts, wiring an event-driven rule, modelling an approval chain, or building an interactive screen flow / wizard…
objectstack-data
Design ObjectStack data schemas — objects, fields, field conditional rules, relationships, validations, indexes, lifecycle hooks, permissions, row-level security, data lifecycle retention/TTL/rotation, metadata protection locks, and external / federated datasources (defineDatasource) — and the seeds (defineSeed())…