network-analytics

network-analytics is a skill for Codex from dzhokhov/markdown-agent-vault-ru. It costs 87 tokens per session (662 once invoked), scanned A, original, MIT.

A network map of people, organizations, events, and topics connected to the AI community.

In plain words
What is it for?
Use it to update relationship data, find central people and emerging groups, identify bridges between clusters, and plan outreach priorities.
Why use it?
It makes scattered mentions and interactions easier to navigate and shows which people connect different groups.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is Навигация: [Индекс скиллов](../README.md).

Good fit Use it to update relationship data, find central people and emerging groups, identify bridges between clusters, and plan outreach priorities.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/dzhokhov/markdown-agent-vault-ru
agentmods
npx agentmods add skills/dzhokhov/markdown-agent-vault-ru/network-analytics

Made for: Codex.

Wrote 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.

agentmods badge for network-analytics

README.md
[![agentmods](https://agentmods.dev/badge/skills/dzhokhov/markdown-agent-vault-ru/network-analytics/github.svg)](https://agentmods.dev/skills/dzhokhov/markdown-agent-vault-ru/network-analytics)
Your own site
<a href="https://agentmods.dev/skills/dzhokhov/markdown-agent-vault-ru/network-analytics"><img src="https://agentmods.dev/badge/skills/dzhokhov/markdown-agent-vault-ru/network-analytics/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.

agentmods 80×15 button for network-analytics

Your own site · 80×15
<a href="https://agentmods.dev/skills/dzhokhov/markdown-agent-vault-ru/network-analytics"><img src="https://agentmods.dev/badge/skills/dzhokhov/markdown-agent-vault-ru/network-analytics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 662 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00087 $0.00662
Opus 5.5 $0.00035 $0.00265
Sonnet 5.5 $0.00017 $0.00132
Haiku 4.5 $0.00009 $0.00066

Measured 1mo ago against content hash 7f5d66134bf2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

network-analytics 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 1mo 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.

skills/network-analytics/SKILL.md · 104 lines

What it actually says

Network Analytics

Навигация: Индекс скиллов

Overview

Преобразуй хаотичные упоминания и взаимодействия в рабочую карту сети влияния.

Скилл отвечает за фазу normalize entities -> update graph -> compute metrics -> outreach plan.

Workflow

1) Normalize Entities

Используй схему из graph-schema.

Сущности:

  • Person
  • Organization
  • Event
  • Topic

2) Update Edges

Поддерживай типизированные связи:

  • co-speaker
  • co-organizer
  • mentioned_with
  • works_at
  • introduced_by
  • attended

Для каждого ребра фиксируй:

  • source
  • date
  • confidence

3) Compute Metrics

Если есть инструменты граф-аналитики, считай:

  • degree centrality
  • betweenness centrality
  • eigenvector centrality
  • communities (Louvain/эквивалент)

Если инструменты недоступны, используй эвристики и явно помечай method=heuristic.

4) Interpret

Используй правила из metrics-and-prioritization:

  • мосты между кластерами,
  • ядро каждого домена,
  • новые растущие кластеры.

5) Build Outreach Plan

Выдай:

  • 5 ключевых мостов
  • 3 кластера/домена
  • 10 приоритетных outreach шагов (к кому, через кого, зачем)

Output

  1. Graph update summary
  2. Top bridges (betweenness)
  3. Community map
  4. Outreach backlog (10 items)

Каждый outreach item:

  • target_person
  • via
  • reason
  • suggested_message_angle
  • expected_outcome

Quality Gates

  • Нет ребра без источника или даты.
  • Нет центральностных выводов без указания метода расчёта.
  • Outreach рекомендации привязаны к конкретной цели, а не общему "познакомиться".

Anti-Patterns

  • Не смешивать однофамильцев без подтверждения identity.
  • Не путать частые упоминания с реальным влиянием.
  • Не делать выводы о кластере на основе 1-2 связей.

References

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 1mo ago First seen · 104 lines · 87 tokens per session scan A 7f5d66134bf2

Subscribe to this mod's changes

network-analytics is a skill published in the GitHub repository dzhokhov/markdown-agent-vault-ru (2 stars, last pushed 1mo ago), licensed MIT. It adds 87 tokens to every session and 662 once invoked, about $0.0003 per session on Opus 5.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.

Related

Other skills, from other repositories

pos-verify

Use this immediately after files are created, edited, moved, deleted, or materially rewritten inside PersonalOS. Verifies that new truth was routed to the correct owner, written in the correct file shape, and still follows POS conventions. Do NOT use for whole-vault deep audits; use system-health-check.

vincentmumme/personalos-boilerplate · 65 tokens

skillify

Use this when {{username}} asks to skillify a repeated workflow, determine whether it deserves a reusable PersonalOS skill, or harden an existing workflow into a tested resolver-reachable capability. Do NOT use for one-off notes, ordinary execution, or already-specified skill authoring; use write-skill.

vincentmumme/personalos-boilerplate · 66 tokens

write-skill

Use this when the user wants to create a new shared PersonalOS skill under skills/ or revise a specified PersonalOS skill and the scope is already clear. Do NOT use for raw workflow capture or deciding whether work should become a skill; use skillify first. Do NOT use for repo-local or agent-local skills unless…

vincentmumme/personalos-boilerplate · 78 tokens

priority-dashboard

Use this to rebuild, inspect, or temporarily steer {{username}}'s current PersonalOS priority dashboard from canonical Actions, Attention Triggers, and owner context. Do NOT use it to create, complete, or independently manage tasks; use task-manager for Action and Trigger lifecycle changes.

vincentmumme/personalos-boilerplate · 60 tokens

log

Use this when a PersonalOS work session, chat outcome, personal reflection, or provided source should be persisted into the modular Daily context and any already-owned canonical files. Do NOT use for single-call processing, single-source knowledge ingestion, Gmail/WhatsApp propagation, or Lexware booking.

vincentmumme/personalos-boilerplate · 59 tokens

task-manager

Use this when {{username}} or an agent wants to add, review, prioritize, complete, defer, park, or inspect todos, open loops, confirmed actions, waiting states, or attention triggers. Maintains atomic records under operations/actions/ and operations/attention-triggers/ as the only local action truth. Do NOT use for…

vincentmumme/personalos-boilerplate · 90 tokens