aspid-profiler-marker

aspid-profiler-marker is a skill for Claude Code, Codex from VPDPersonal/Aspid.FastTools. It costs 82 tokens per session (1,288 once invoked), scanned A, original, MIT.

A Unity source-generated helper for adding named performance markers to code. These markers appear in Unity's Profiler, which records timing and other runtime performance information.

In plain words
What is it for?
Use it to measure Unity methods, code sections, loops, jobs, and other execution paths while investigating runtime performance.
Why use it?
It avoids manually declaring profiler marker fields, names, or conditional release builds. Nested scopes can show the timing of a whole method, section, or repeated loop work.

Skill for Claude CodeCodex

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

Good fit Use it to measure Unity methods, code sections, loops, jobs, and other execution paths while investigating runtime performance.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vpdpersonal/aspid.fasttools/aspid-profiler-marker
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 VPDPersonal/Aspid.FastTools --skill aspid-profiler-marker
Clone the repo
git clone --depth 1 https://github.com/VPDPersonal/Aspid.FastTools

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 aspid-profiler-marker

README.md
[![agentmods](https://agentmods.dev/badge/skills/vpdpersonal/aspid.fasttools/aspid-profiler-marker/github.svg)](https://agentmods.dev/skills/vpdpersonal/aspid.fasttools/aspid-profiler-marker)
Your own site
<a href="https://agentmods.dev/skills/vpdpersonal/aspid.fasttools/aspid-profiler-marker"><img src="https://agentmods.dev/badge/skills/vpdpersonal/aspid.fasttools/aspid-profiler-marker/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 aspid-profiler-marker

Your own site · 80×15
<a href="https://agentmods.dev/skills/vpdpersonal/aspid.fasttools/aspid-profiler-marker"><img src="https://agentmods.dev/badge/skills/vpdpersonal/aspid.fasttools/aspid-profiler-marker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,288 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.00082 $0.01288
Opus 5.5 $0.00033 $0.00515
Sonnet 5.5 $0.00016 $0.00258
Haiku 4.5 $0.00008 $0.00129

Measured 4d ago against content hash 774118772a7f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

aspid-profiler-marker 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 4d 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/aspid-profiler-marker/SKILL.md · 76 lines

How it starts

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

this.Marker()

this.Marker() returns a ProfilerMarker.AutoScope for a marker that a source generator creates for that exact call site. No field, name string, attribute or partial is needed; works in classes, structs (including Burst jobs) and ref structs.

  • If the user's scripts have an .asmdef, it must reference Aspid.FastTools. No using is needed.
  • Without ENABLE_PROFILER (release players) every call returns default; do not add guards.
public void Step()
{
    using var _ = this.Marker();                          // FlockSimulation.Step (12)

    using (this.Marker().WithName("Steering"))            // FlockSimulation.Steering (14)
        foreach (var agent in _agents)
            using (this.Marker().WithName("Steering.Agent"))   // one row, Calls = agent count
                ComputeSteering(agent);
}

Profiler nesting follows using nesting. Markers in loops, lambdas and local functions are fine. A scope held across yield return or await resumes in a later frame or on another thread and leaves the samples unbalanced — warning AFT0013; put the marker inside each synchronous step.

Names

Type.Member (line), where line is the line of the Marker() call:

  • constructor -> Ctor; static constructor -> StaticCtor; finalizer -> Finalize; property or indexer accessor -> property name / Indexer; event accessor -> event name; field or auto-property initializer -> field / property name; operator -> op_Addition and the like; lambda or local function -> the enclosing member; explicit interface implementation -> the interface member name;
  • nested type -> only the innermost type name (Agent.Move (line)), so same-named types in different namespaces or outer types show the same name;
  • generic class -> one marker per closed type (Worker<List<Int32>>.Run (line)); generic struct -> one marker for all (Job<T>.Execute (line)), so Burst can compile it.

WithName("X") replaces only the member part (FlockSimulation.X (line)). It is read from source at compile time, chained directly on this.Marker(): a literal, a const, nameof(...), or a concatenation or interpolation of them counts. Any other value (a variable, a static readonly field, a format or alignment in a hole) keeps the member name — warning AFT0014. For runtime-computed names use a hand-written static readonly ProfilerMarker.

Read the full file on GitHub · 76 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. 4d ago Changed · +1 lines 774118772a7f
  2. 5d ago Changed · +1 lines 3a9593c86046
  3. 17d ago Changed · +3 lines 2ed4f3dfe30a
  4. 20d ago First seen · 71 lines · 82 tokens per session scan A d11873047933

Subscribe to this mod's changes

aspid-profiler-marker is a skill published in the GitHub repository VPDPersonal/Aspid.FastTools (24 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 1,288 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-09-26.

Related

Other skills, from other repositories

test-designing-guide

Provides test design methodology for Unity projects. Use this skill whenever designing test cases from requirements or specifications, including selecting test techniques, deriving test cases, and formatting them. Even for small features, load this skill to ensure test design rigor.

nowsprinting/unity-coding-skills · 52 tokens

test-writing-guide

Provides guidelines for writing test code for Unity projects. Make sure to use this skill whenever writing, creating, editing, or modifying test code files (files under Tests/). This includes implementing new tests, fixing test failures, adding test cases, or any task that results in test code changes. Even for small…

nowsprinting/unity-coding-skills · 81 tokens

edit-scene

Creates and modifies Unity scene and prefab files. Use this skill whenever creating, editing, or modifying .unity scene files or .prefab prefab files. This includes adding GameObjects, building uGUI hierarchies, wiring up components, and any task that results in changes to .unity or .prefab files.

nowsprinting/unity-coding-skills · 67 tokens

run-tests

Provides guidelines for running Unity tests using the rununitytests tool. Make sure to use this skill whenever running, executing, or re-running tests on the Unity editor. This includes verifying implementations, debugging test failures, running specific test assemblies, or any task that involves the rununitytests…

nowsprinting/unity-coding-skills · 130 tokens

resolve-diagnostics

Resolves IDE diagnostics (inspections and analyzer findings) at the warning or higher severity level for a given set of files, then applies the solution's code style. Use this skill when a workflow's refactoring step calls for resolving diagnostics, or when the user asks to fix warnings, inspections, or static…

nowsprinting/unity-coding-skills · 84 tokens

unity-yaml-editing-guide

Provides guidelines for directly editing Unity YAML-serialized asset files for Unity projects. Make sure to use this skill whenever creating, editing, or modifying simple YAML asset files (ScriptableObjects, Materials, etc.) via Edit/Write tools without going through the Unity Editor. This includes adjusting…

nowsprinting/unity-coding-skills · 113 tokens