graph.analytics.pagerank

A graph command that ranks nodes by importance using PageRank, an algorithm that considers links from other important nodes.

In plain words
What is it for?
Use it to calculate standard or personalized importance scores on a fixed, current, or historical graph snapshot.
Why use it?
It helps compare the relative importance of nodes in a network using a repeatable calculation.

Command

Install

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.

agentmods
npx agentmods add commands/stratalab/strata-core/graph.analytics.pagerank
Clone the repo
git clone --depth 1 https://github.com/stratalab/strata-core
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 127 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00127
Opus 5 $0.00000 $0.00063
Sonnet 5 $0.00000 $0.00025
Haiku 4.5 $0.00000 $0.00013

Measured 2d ago against content hash b1ec87750c97, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

graph.analytics.pagerank 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.

crates/executor/idl/v1/prose/commands/graph.analytics.pagerank.md · 7 lines

What it actually says

Computes PageRank over a consistent snapshot. Tunable damping (default 0.85), iteration bound (default 20), and convergence tolerance (default 1e-6); the response reports how many iterations actually ran. Optional personalization seeds steer both teleport and dangling mass toward weighted nodes, and the response flags personalized: true. Results are deterministic for a fixed graph state. Accepts an optional snapshot budget and as_of for time travel.

Changes

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.

  1. 2d ago First seen · 7 lines · 0 tokens per session scan A b1ec87750c97

Subscribe to this mod's changes

graph.analytics.pagerank is a command published in the GitHub repository stratalab/strata-core (2 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 127 tokens. 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.