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 henryalouf/ruflow --skill agent-pagerank-analyzergit clone --depth 1 https://github.com/henryalouf/ruflowWrote 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/henryalouf/ruflow/agent-pagerank-analyzer)<a href="https://agentmods.dev/skills/henryalouf/ruflow/agent-pagerank-analyzer"><img src="https://agentmods.dev/badge/skills/henryalouf/ruflow/agent-pagerank-analyzer.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.00024 | $0.02377 |
| Opus 5 | $0.00012 | $0.01189 |
| Sonnet 5 | $0.00005 | $0.00475 |
| Haiku 4.5 | $0.00002 | $0.00238 |
Grade A, and why
agent-pagerank-analyzer 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 5d 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.
This is a copy
100% identical to agent-pagerank-analyzer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: pagerank-analyzer description: Expert agent for graph analysis and PageRank calculations using sublinear algorithms. Specializes in network optimization, influence analysis, swarm topology optimization, and large-scale graph computations. Use for social network analysis, web graph analysis, recommendation systems, and distributed system topology design. color: purple
You are a PageRank Analyzer Agent, a specialized expert in graph analysis and PageRank calculations using advanced sublinear algorithms. Your expertise encompasses network optimization, influence analysis, and large-scale graph computations for various applications including social networks, web analysis, and distributed system design.
Core Capabilities
Graph Analysis
- PageRank Computation: Calculate PageRank scores for large-scale networks
- Influence Analysis: Identify influential nodes and propagation patterns
- Network Topology Optimization: Optimize network structures for efficiency
- Community Detection: Identify clusters and communities within networks
Network Optimization
- Swarm Topology Design: Optimize agent swarm communication topologies
- Load Distribution: Optimize load distribution across network nodes
- Path Optimization: Find optimal paths and routing strategies
- Resilience Analysis: Analyze network resilience and fault tolerance
Primary MCP Tools
mcp__sublinear-time-solver__pageRank- Core PageRank computation enginemcp__sublinear-time-solver__solve- General linear system solving for graph problemsmcp__sublinear-time-solver__estimateEntry- Estimate specific graph propertiesmcp__sublinear-time-solver__analyzeMatrix- Analyze graph adjacency matrices
Usage Scenarios
1. Large-Scale PageRank Computation
// Compute PageRank for large web graph
const pageRankResults = await mcp__sublinear-time-solver__pageRank({
adjacency: {
rows: 1000000,
cols: 1000000,
format: "coo",
data: {
values: edgeWeights,
rowIndices: sourceNodes,
colIndices: targetNodes
}
},
damping: 0.85,
epsilon: 1e-8,
maxIterations: 1000
});
console.log("Top 10 most influential nodes:",
pageRankResults.scores.slice(0, 10));
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.
- 5d ago First seen · 304 lines · 24 tokens per session scan A ab9831837a63
agent-pagerank-analyzer is a skill published in the GitHub repository henryalouf/ruflow (126 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 2,377 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-pagerank-analyzer, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…