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 tetracoralla/deterministic-dependency-engine --skill reason-about-dependenciesgit clone --depth 1 https://github.com/tetracoralla/deterministic-dependency-engineWrote 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/tetracoralla/deterministic-dependency-engine/reason-about-dependencies)<a href="https://agentmods.dev/skills/tetracoralla/deterministic-dependency-engine/reason-about-dependencies"><img src="https://agentmods.dev/badge/skills/tetracoralla/deterministic-dependency-engine/reason-about-dependencies.svg" alt="Measured on agentmods" 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.00067 | $0.00268 |
| Opus 5 | $0.00034 | $0.00134 |
| Sonnet 5 | $0.00013 | $0.00054 |
| Haiku 4.5 | $0.00007 | $0.00027 |
Grade A, and why
reason-about-dependencies 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 7d 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.
What it actually says
Reason about declared dependencies with Deterministic Dependency Engine
Call the matching direct tool once. Supply the graph with explicit
dependent and prerequisite fields; never translate it to from / to.
- Use
dependency_resolvefor what remains, what is ready, and execution order. - Use
dependency_impactfor downstream effects of changed nodes. - Use
dependency_explainfor blocker paths or one impact path. - Use
dependency_slicewhen only the minimal relevant graph is needed. - Use
graph_validatewhen legality, cycles, or ordering is the question.
Treat satisfied and changed as query-local facts, not graph properties. A
cycle or invalid graph is a result to repair, not permission to guess an order.
Present the actionable structured result compactly. A calculation receipt only
identifies the computation; never describe it as proof that the declared
relations are true.
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.
- 7d ago First seen · 22 lines · 67 tokens per session scan A 7af0ddab6ab9
reason-about-dependencies is a skill published in the GitHub repository tetracoralla/deterministic-dependency-engine (0 stars, last pushed 3d ago), licensed Apache-2.0. It adds 67 tokens to every session and 268 once invoked, about $0.0003 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
typescript-style
Validate TypeScript/React code against style and architectural conventions.
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…
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
no-bare-casts
Writing as in TypeScript or TSX production code, modifying a file that contains a bare as cast, silencing a type error with a cast, encountering as unknown as, or reviewing a cast site.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
analyze-market
Perform a market analysis for a product category or segment. Trigger on: market analysis, market size, TAM SAM SOM, market opportunity, industry analysis.