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.
npx agentmods add skills/plamentsv/plamen/token-flow-tracingnpx skills add PlamenTSV/plamen --skill token-flow-tracinggit clone --depth 1 https://github.com/PlamenTSV/plamenWrote 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.
[](https://agentmods.dev/skills/plamentsv/plamen/token-flow-tracing)<a href="https://agentmods.dev/skills/plamentsv/plamen/token-flow-tracing"><img src="https://agentmods.dev/badge/skills/plamentsv/plamen/token-flow-tracing.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00025 | $0.03088 |
| Opus 5 | $0.00013 | $0.01544 |
| Sonnet 5 | $0.00005 | $0.00618 |
| Haiku 4.5 | $0.00003 | $0.00309 |
Grade A, and why
token-flow-tracing 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TOKEN_FLOW_TRACING Skill
Trigger Pattern: BALANCE_DEPENDENT flag (required) Inject Into: Depth-token-flow, breadth agents Purpose: Trace all token flows through Aptos Move protocols using FungibleAsset and Coin models, identifying accounting desync, unsolicited deposit vectors, type confusion, and dispatchable hook side effects
For every token the protocol handles:
1. Asset Inventory
Enumerate ALL asset types the protocol handles:
| Asset | Model | Type Parameter / Metadata | Decimals | Entry Modules | Exit Modules |
|---|---|---|---|---|---|
| {name} | Coin / FungibleAsset | {CoinType or metadata Object} | {decimals} | {list} | {list} |
Aptos dual token model:
- Legacy Coin: Uses
CoinStore<T>resource at user address. Type parameterTidentifies the coin. - FungibleAsset (FA): Uses
FungibleStoreobjects.Metadataobject identifies the asset type. - Paired assets: Some tokens exist as both Coin and FA simultaneously (APT is the primary example). Check if protocol handles both representations correctly.
- Migration tokens: Tokens migrated from Coin to FA model may have both interfaces active.
2. Token Entry Points
Where can tokens enter the protocol?
| Entry Path | Function | Asset Model | Accounting Updated? | Access Control |
|---|---|---|---|---|
| Standard deposit | {deposit_fn} | {Coin/FA} | YES/NO | {who can call} |
primary_fungible_store::deposit() |
External | FA | NO (protocol unaware) | Permissionless |
coin::deposit<T>() |
External | Coin | NO (protocol unaware) | Permissionless (if CoinStore registered) |
Direct fungible_asset::deposit() |
Via store ref | FA | NO (protocol unaware) | Requires FungibleStore reference |
move_to<T>() |
Internal | Resource | {depends} | Module only |
| Side-effect receipts | External call returns | {varies} | {depends} | {depends} |
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.
- 6d ago First seen · 253 lines · 25 tokens per session scan A f485fc85ed23
token-flow-tracing is a skill published in the GitHub repository PlamenTSV/plamen (281 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 3,088 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-30.
Other skills, from other repositories
prowler-ui
Prowler UI-specific patterns. For generic patterns, see: typescript, react-19, nextjs-16, tailwind-4. Trigger: When working inside ui/ on Prowler-specific conventions (shadcn, folder placement, actions/adapters, shared types/hooks/lib).
prowler-pr
Creates Pull Requests for Prowler following the project template and conventions. Trigger: When working on pull request requirements or creation (PR template sections, PR title Conventional Commits check, changelog gate/no-changelog label), or when inspecting PR-related GitHub workflows like conventional-commit.yml…
tailwind-4
Tailwind CSS 4 patterns and best practices. Trigger: When styling with Tailwind (className, variants, cn()), especially when dynamic styling or CSS variables are involved (no var() in className).
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
prowler
Main entry point for Prowler development - quick reference for all components. Trigger: General Prowler development questions, project overview, component navigation (NOT PR CI gates or GitHub Actions workflows).
prowler-tour
Keeps product-tour definitions aligned with the UI features they describe. Trigger: When modifying UI components that have associated tours, editing tour definition files, or renaming data-tour-id attributes.