agentmods.dev

about

about is a command for coding agents from vladm3105/aidoc-flow-framework. It costs 15 tokens per session (564 once invoked), scanned A, original, MIT.

A command that displays a plugin's version, framework specification, license, repository, homepage, and other identity details.

In plain words
What is it for?
It helps identify a plugin and confirm the framework version it follows.
Why use it?
It provides the exact information needed to check an installation or report a problem without guessing which version is running.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the aidoc-flow plugin — 30 skills, 12 commands, 11 agents, 1 hook shipped together

not rated 17 3d ago A scan 15 tokens original MIT
View the source file vladm3105/aidoc-flow-framework
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.

agentmods
npx agentmods add commands/vladm3105/aidoc-flow-framework/about
Clone the repo
git clone --depth 1 https://github.com/vladm3105/aidoc-flow-framework

Or install aidoc-flow, the plugin that ships this one along with the rest of its 30 skills, 12 commands, 11 agents, 1 hook.

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 about

README.md
[![agentmods](https://agentmods.dev/badge/commands/vladm3105/aidoc-flow-framework/about.svg)](https://agentmods.dev/commands/vladm3105/aidoc-flow-framework/about)
Your own site
<a href="https://agentmods.dev/commands/vladm3105/aidoc-flow-framework/about"><img src="https://agentmods.dev/badge/commands/vladm3105/aidoc-flow-framework/about.svg" alt="Measured on agentmods" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 564 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00015 $0.00564
Opus 5 $0.00008 $0.00282
Sonnet 5 $0.00003 $0.00113
Haiku 4.5 $0.00002 $0.00056

Measured 3d ago against content hash d477e4d33a70, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

about 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 3d 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.

platforms/claude-code-plugin/commands/about.md · 64 lines

How it starts

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

About

Print a one-screen summary identifying this plugin and the framework spec it conforms to. Useful as the first thing to share when filing a bug report or checking that the right version is installed.

Instructions

  1. Read the plugin's identity files (do not invent values):

    • ${CLAUDE_PLUGIN_ROOT}/VERSION — the plugin's own SemVer.
    • ${CLAUDE_PLUGIN_ROOT}/FRAMEWORK_SPEC_VERSION — the spec version the plugin declares conformance to.
    • ${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json — the manifest. Pull name, description, version, license, repository, homepage, author.name, author.url.

  2. Render the about screen as a table. Use the exact values you read; if any file is missing, print (unknown) in that cell rather than guessing.

    aidoc-flow — Claude Code plugin

| Field              | Value                                          |
|--------------------|------------------------------------------------|
| Plugin             | <name>                                         |
| Plugin version     | <VERSION>                                      |
| Framework spec     | <FRAMEWORK_SPEC_VERSION>                       |
| License            | <license>                                      |
| Repository         | <repository>                                   |
| Homepage           | <homepage>                                     |
| Author             | <author.name> (<author.url>)                   |

<description from plugin.json>

  3. Append three navigation pointers (one line each) so the user knows where to go next:

    • Run /aidoc-flow:help — orient yourself in the 8-layer flow
    • Run /aidoc-flow:bug-report — file a bug with this version stamp
    • Run /aidoc-flow:status — see where the current project is in the flow

  4. Do not print anything else. No marketing, no per-skill summaries (that's /aidoc-flow:help's job).

Error handling

Read the full file on GitHub · 64 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. 3d ago First seen · 64 lines · 15 tokens per session scan A d477e4d33a70

Subscribe to this mod's changes

about is a command published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 564 once invoked, about $0.0001 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.

activemeta
Related

Other commands, from other repositories

create-command

Create a new obsidian-second-brain command via interview - zero markdown editing required.

eugeniughelbur/obsidian-second-brain · 16 tokens

obsidian-health

Run a vault health check - grouped by severity, detects contradictions, concept gaps, stale claims, and structural issues.

eugeniughelbur/obsidian-second-brain · 22 tokens

obsidian-visualize

Generate a visual canvas map of your vault - see the shape of your second brain and how knowledge connects.

eugeniughelbur/obsidian-second-brain · 20 tokens

obsidian-architect

Scan a codebase and write a maintained set of architecture notes into the vault - overview, per-module notes, key decisions. Re-run to refresh without clobbering your edits.

eugeniughelbur/obsidian-second-brain · 36 tokens

obsidian-export

Export a clean structured snapshot of the vault that any agent or tool can consume - flat JSON, markdown index, or an OKF (Open Knowledge Format) bundle.

eugeniughelbur/obsidian-second-brain · 32 tokens

obsidian-retrieval-eval

Measure how well vault search finds the right note for a natural-language question - recall@k and MRR, with the concrete failures.

eugeniughelbur/obsidian-second-brain · 26 tokens