characterizing-running-times

characterizing-running-times is a skill for Claude Code, Codex from Arcadi4/nerdy. It costs 49 tokens per session (2,233 once invoked), scanned A, original, MIT.

A guide for describing how an algorithm’s time or memory use grows as its input gets larger, using terms such as Big O, Omega, and Theta.

In plain words
What is it for?
Analyzing loops, recurrences, pseudocode, and algorithms; comparing growth rates; and checking or proving asymptotic bounds.
Why use it?
It helps distinguish worst-case, best-case, and all-input guarantees, and prevents imprecise claims about performance.

Skill for Claude CodeCodex

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

Good fit Analyzing loops, recurrences, pseudocode, and algorithms; comparing growth rates; and checking or proving asymptotic bounds.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/arcadi4/nerdy/characterizing-running-times
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 Arcadi4/nerdy --skill characterizing-running-times
Clone the repo
git clone --depth 1 https://github.com/Arcadi4/nerdy

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 characterizing-running-times

README.md
[![agentmods](https://agentmods.dev/badge/skills/arcadi4/nerdy/characterizing-running-times.svg)](https://agentmods.dev/skills/arcadi4/nerdy/characterizing-running-times)
Your own site
<a href="https://agentmods.dev/skills/arcadi4/nerdy/characterizing-running-times"><img src="https://agentmods.dev/badge/skills/arcadi4/nerdy/characterizing-running-times.svg" alt="Measured on agentmods" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,233 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.00049 $0.02233
Opus 5 $0.00024 $0.01117
Sonnet 5 $0.00010 $0.00447
Haiku 4.5 $0.00005 $0.00223

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

Security

Grade A, and why

characterizing-running-times 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.

clrs/characterizing-running-times/SKILL.md · 318 lines

How it starts

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

Characterizing Running Times

Overview

Use asymptotic notation to state the simplest precise growth bound for an algorithm or function. Always name the quantity being bounded: worst case, best case, all inputs, space, recurrence term, or another explicit quantity.

Shared CLRS Conventions

Follow the parent clrs skill for mathematical formatting, formula-free headings, direct polished answers, and CLRS-wide answer style.

When to Use

  • Analyzing algorithms, loops, recurrences, or pseudocode running time.
  • Comparing growth rates: logarithms, polynomials, exponentials, factorials, iterated logarithms, and Fibonacci numbers.
  • Proving or checking asymptotic claims.
  • Fixing sloppy statements such as saying a lower bound is "at least Big O" or claiming an unqualified running time when only the worst case is tight.

Core Workflow

  1. Name the case. Say "worst-case running time," "best-case running time," or "running time for all inputs." A worst-case tight bound does not imply every input has that running time.
  2. Drop detail only after bounding. Constants and lower-order terms vanish asymptotically, but justify the step with constants, thresholds, or known growth rules.
  3. Choose notation by claim strength. Use O for upper bound, Omega for lower bound, Theta for tight bound, little-o for non-tight upper bound, and little-omega for non-tight lower bound.
  4. For Theta, prove both sides. Use Theorem 3.1:

$$ f(n) = \Theta(g(n)) \iff f(n) = O(g(n)) \text{ and } f(n) = \Omega(g(n)). $$

  1. For algorithm lower bounds, construct hard inputs. A worst-case lower bound means: for every sufficiently large input size, at least one input of that size takes that much time.
  2. Use the simplest precise expression. Prefer:

$$ \Theta(n^2) $$

over:

$$ \Theta(3n^2 + 20n). $$

Prefer Theta over O when the bound is tight.

Notation Reference

Assume functions are asymptotically nonnegative.

O-notation: asymptotic upper bound. There are positive constants and a threshold such that eventually:

Read the full file on GitHub · 318 lines

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. 7d ago First seen · 318 lines · 49 tokens per session scan A 7e3b609f5481

Subscribe to this mod's changes

characterizing-running-times is a skill published in the GitHub repository Arcadi4/nerdy (7 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 2,233 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

coding-frameworks

Reference frameworks for coding interviews — the UMPIRE method, a pattern taxonomy (two-pointers, sliding-window, BFS/DFS, backtracking, dynamic-programming, graphs, and more), a Big-O cheatsheet, Python idioms, communication guidance, and anti-patterns. Used by the coding commands (/coding-explain, /practice-coding…

kirilxd/swe-interview-coach · 103 tokens

behavioral-frameworks

Reference frameworks (STAR, SBI, CARL), anti-patterns, and standard interviewer follow-ups for behavioral interview prep. Use when extracting STAR stories from user's experience, mapping stories to a specific company or JD, running mock behavioral interviews, rehearsing behavioral story delivery, or debriefing a real…

kirilxd/swe-interview-coach · 67 tokens

algo-sensei

Your personal DSA & LeetCode mentor. Use for problem explanations, progressive hints, code reviews, mock interviews, pattern recognition, complexity analysis, and custom problem generation. Automatically adapts to your learning style and request type.

karanb192/algo-sensei · 51 tokens

nerd

Explains any code, system, or flow as ASCII flowcharts that expose the fundamental data structures and algorithms underneath. Use /skill:nerd to get a bird's-eye-view map of how something works, then zoom into any specific algorithm or data structure for a deeper breakdown. Strips jargon, shows the actual machine …

savagemechanic/nerd · 87 tokens

hr-onboarding

A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".

nexu-io/open-design · 62 tokens

eli5

Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.

companion-inc/feynman · 63 tokens