linguistic-semantic-algorithms

linguistic-semantic-algorithms is a skill for Claude Code, Codex from pproenca/dot-skills. It costs 130 tokens per session (2,584 once invoked), scanned A, original, MIT.

A set of algorithms for understanding unfamiliar source code and its history. It uses language analysis, mathematical graphs, and code comparisons to reveal themes, relationships, duplicates, and risk signals.

In plain words
What is it for?
Use it to explore a new codebase, find likely files for a bug, scope a feature, review refactors, detect copied code, and study changes across commits.
Why use it?
It helps when simple text search or intuition cannot show where a concept appears, which files matter, or how parts of a codebase are connected.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to explore a new codebase, find likely files for a bug, scope a feature, review refactors, detect copied code, and study changes across commits.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pproenca/dot-skills/linguistic-semantic-algorithms
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.

Any agent
npx skills add pproenca/dot-skills --skill linguistic-semantic-algorithms
Clone the repo
git clone --depth 1 https://github.com/pproenca/dot-skills

Made for: Claude Code, 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 linguistic-semantic-algorithms

README.md
[![agentmods](https://agentmods.dev/badge/skills/pproenca/dot-skills/linguistic-semantic-algorithms/github.svg)](https://agentmods.dev/skills/pproenca/dot-skills/linguistic-semantic-algorithms)
Your own site
<a href="https://agentmods.dev/skills/pproenca/dot-skills/linguistic-semantic-algorithms"><img src="https://agentmods.dev/badge/skills/pproenca/dot-skills/linguistic-semantic-algorithms/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 linguistic-semantic-algorithms

Your own site · 80×15
<a href="https://agentmods.dev/skills/pproenca/dot-skills/linguistic-semantic-algorithms"><img src="https://agentmods.dev/badge/skills/pproenca/dot-skills/linguistic-semantic-algorithms.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 130 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,584 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00130 $0.02584
Opus 5 $0.00065 $0.01292
Sonnet 5 $0.00026 $0.00517
Haiku 4.5 $0.00013 $0.00258

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

Security

Grade A, and why

linguistic-semantic-algorithms 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.

skills/.experimental/linguistic-semantic-algorithms/SKILL.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

pproenca Linguistic and Semantic Algorithms Best Practices

Reference of 40 algorithms an agent should reach for when extracting structure, meaning, history, or risk signals from source code and commit data. Categories are ordered by insight-per-effort — how much non-obvious truth the technique exposes relative to how easy it is to apply. The first two categories target the highest-leverage questions: what business entities live in this code? and where else does this concept already exist? — questions that grep and intuition cannot answer.

When to Apply

Reach for these algorithms when:

  • Orienting in an unfamiliar codebase: PageRank the import graph to find the core, run LDA over identifier tokens to discover business themes, mine change coupling to surface hidden architectural couplings.
  • Hunting a bug from a description: BM25 + history prior + embedding re-rank produces a ranked file shortlist far better than grep.
  • Scoping a feature: find prior PRs that did similar work via embedding similarity; map the feature's vocabulary against the codebase's domain via TF-IDF and noun-phrase mining.
  • Reviewing a refactor: AST-level GumTree diff reveals semantic impact text diff hides; PDG isomorphism finds the "same logic, different code" twin you should also update.
  • Auditing risk: hotspots (churn × complexity), bus factor, defect-magnet density, dead-code candidates — together they direct attention to the parts of the codebase that pay back attention.
  • Identifying domain entities and bounded contexts: noun-phrase mining + TF-IDF rare-term extraction + Louvain communities + Jensen-Shannon divergence on per-cluster vocabulary.

Rule Categories by Priority

Priority Category Impact Prefix Question answered
1 Concept & Domain Extraction CRITICAL concept- What business entities live in this code?
2 Semantic Similarity & Feature Mapping CRITICAL sim- Where else does this concept already exist?
3 Architectural Topology HIGH graph- What is the shape of this codebase?
4 Co-Change & Temporal Mining HIGH mine- What hidden couplings does history reveal?
5 Clone & Duplication Detection MEDIUM-HIGH clone- Where are we repeating ourselves?
6 Bug & Feature Localization MEDIUM-HIGH local- Given a description, where in code?
7 Identifier Linguistics MEDIUM ling- How to prepare tokens so the other algorithms work?
8 Complexity & Risk Metrics MEDIUM risk- Where is the danger concentrated?

Read the full file on GitHub · 125 lines

Files

What ships with it

44 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. 5d ago First seen · 125 lines · 130 tokens per session scan A 2c0344b59652

Subscribe to this mod's changes

linguistic-semantic-algorithms is a skill published in the GitHub repository pproenca/dot-skills (205 stars, last pushed 24d ago), licensed MIT. It adds 130 tokens to every session and 2,584 once invoked, about $0.0006 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-09-03.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens