Review AI agent spending by conversation, with each session’s start time, message count, main model, and total cost. Use the results to identify expensive sessions and understand typical costs before planning longer work.
Per-conversation cost view — list every session in cost-tracking with started-at, message count, top model, and total cost
Review the instructions the agent will receive before you install.
cost-report and cost-optimize aggregate by agent and model. This skill aggregates by conversation (session) — a different lens that surfaces which conversations cost the most. Useful for retrospectives ("which sessions ran long on Opus?") and for evaluating whether a given project's session pattern is sustainable.
CONV_NAMESPACE=cost-tracking-<project>.Run the script from anywhere:
node plugins/ruflo-cost-tracker/scripts/conversation.mjs
Optional env:
CONV_FORMAT=json — emit JSON instead of markdownCONV_LIMIT=20 — show only the most recent N conversationsCONV_NAMESPACE=cost-tracking — override target namespaceInspect the markdown table — total cost across all conversations, per-tier rollup, then a per-session table (started-at, sessionId prefix, message count, top model, cost).
cost-track — the producer that populates cost-tracking:session-*cost-report — same data, per-agent / per-model lenscost-trend — drift across bench runs (different axis: corpus runs vs conversations)cost-budget-check — sums across conversations to evaluate the budget thresholdNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.