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 skills add navraj007in/architecture-cowork-plugin --skill continuous-cost-monitorgit clone --depth 1 https://github.com/navraj007in/architecture-cowork-pluginWrote 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/navraj007in/architecture-cowork-plugin/continuous-cost-monitor)<a href="https://agentmods.dev/skills/navraj007in/architecture-cowork-plugin/continuous-cost-monitor"><img src="https://agentmods.dev/badge/skills/navraj007in/architecture-cowork-plugin/continuous-cost-monitor/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.
<a href="https://agentmods.dev/skills/navraj007in/architecture-cowork-plugin/continuous-cost-monitor"><img src="https://agentmods.dev/badge/skills/navraj007in/architecture-cowork-plugin/continuous-cost-monitor.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.03686 |
| Opus 5 | $0.00010 | $0.01843 |
| Sonnet 5 | $0.00004 | $0.00737 |
| Haiku 4.5 | $0.00002 | $0.00369 |
Grade A, and why
continuous-cost-monitor 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 8d 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 — 492 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Continuous Cost Monitor Skill
Tracks actual infrastructure costs against estimated costs. Alerts when actual spend drifts from projection, identifies cost drivers, and suggests corrective actions.
When to Use
Use this skill to:
- Detect cost creep — infrastructure spending slowly increases over time
- Root-cause cost spikes — which service changed? traffic? resource use?
- Compare actual vs. estimated — am I spending what I projected?
- Trigger optimization cycles — when do I need to re-optimize?
- Alert on budget overruns — notify team before exceeding budget
Input
Provide estimated costs + actual spend data:
{
"estimated_monthly_cost": 8500,
"actual_monthly_cost": 9200,
"cost_breakdown_estimated": {
"backend_compute": 1200,
"database": 1800,
"cache": 200,
"cdn": 300,
"monitoring": 300,
"storage": 500,
"other": 400
},
"cost_breakdown_actual": {
"backend_compute": 1500,
"database": 2100,
"cache": 200,
"cdn": 350,
"monitoring": 400,
"storage": 450,
"other": 200
},
"traffic_metrics": {
"dau_estimated": 100000,
"dau_actual": 110000,
"query_volume_estimated": 500000,
"query_volume_actual": 650000
},
"measurement_period_days": 30,
"budget_threshold": 9000
}
Output
A cost monitoring report:
{
"period": "April 2026",
"estimated_vs_actual": {
"estimated": 8500,
"actual": 9200,
"variance": 700,
"variance_percent": 8.2,
"status": "YELLOW (over by $700)"
},
"cost_breakdown_analysis": {
"backend_compute": {
"estimated": 1200,
"actual": 1500,
"variance": 300,
"variance_percent": 25,
"driver": "Traffic 10% higher than expected (110k vs 100k DAU)"
},
"database": {
"estimated": 1800,
"actual": 2100,
"variance": 300,
"variance_percent": 16.7,
"driver": "Query volume 30% higher (650k vs 500k queries). Likely N+1 queries or missing cache."
},
"cache": {
"estimated": 200,
"actual": 200,
"variance": 0,
"variance_percent": 0,
"status": "On budget"
},
"cdn": {
"estimated": 300,
"actual": 350,
"variance": 50,
"variance_percent": 16.7,
"driver": "Traffic 10% higher (correlates with DAU increase)"
},
"monitoring": {
"estimated": 300,
"actual": 400,
"variance": 100,
"variance_percent": 33,
"driver": "Increased metric cardinality (added new dashboards or higher scrape frequency)"
},
"storage": {
"estimated": 500,
"actual": 450,
"variance": -50,
"variance_percent": -10,
"status": "Better than expected"
},
"other": {
"estimated": 400,
"actual": 200,
"variance": -200,
"variance_percent": -50,
"status": "Significantly better than expected"
}
},
"root_cause_analysis": {
"primary_driver": "Database query volume 30% higher than expected",
"contributing_factors": [
"Traffic 10% higher (110k vs 100k DAU) — accounts for ~$300",
"Inefficient queries — N+1 patterns or missing caching — accounts for ~$200",
"Monitoring cost creep — added dashboards — accounts for ~$100"
],
"confidence": 0.85
},
"trend_analysis": {
"month_1_actual": 8100,
"month_2_actual": 8800,
"month_3_actual": 9200,
"trend": "Increasing",
"monthly_growth": 5.5,
"projected_next_month": 9700,
"annualized_growth": 66
},
"alerts": [
{
"level": "YELLOW",
"message": "Cost overrun: +$700 (+8.2%) vs. estimate",
"action": "Review database query patterns and cache hit rates"
},
{
"level": "ORANGE",
"message": "Database costs growing (16.7% overrun). Query volume 30% higher.",
"action": "Profile slow queries, implement caching, optimize N+1 patterns"
},
{
"level": "ORANGE",
"message": "Monitoring cost increasing (33% overrun). Cardinality growth?",
"action": "Audit new metrics added. Disable unused dashboards."
},
{
"level": "YELLOW",
"message": "Cost trend: +5.5% per month. At this rate, exceed $10k budget in 2 months.",
"action": "Run cost optimization (reduce scope or increase efficiency)"
}
],
"budget_status": {
"budget": 9000,
"actual": 9200,
"over_budget": true,
"headroom": -200,
"trajectory": "Will exceed budget next month at current trend"
},
"recommendations": [
{
"action": "Optimize database queries",
"potential_savings": 200,
"effort": "Medium (1-2 weeks)",
"confidence": "High"
},
{
"action": "Review monitoring cardinality",
"potential_savings": 100,
"effort": "Low (1-2 days)",
"confidence": "High"
},
{
"action": "Consider caching layer for read-heavy queries",
"potential_savings": 150,
"effort": "Medium (1 week)",
"confidence": "Medium"
},
{
"action": "Scale traffic analysis — is 110k DAU sustainable?",
"potential_savings": 300,
"effort": "Low (planning only)",
"confidence": "Medium"
}
],
"escalation_actions": {
"if_over_10_percent": "Run `/architect:optimize-costs` to identify quick wins",
"if_trend_continues": "Trigger roadmap planning discussion (may need rearchitecture)",
"if_exceeded_budget": "Notify finance and product teams; discuss scope/timeline 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.
- 8d ago First seen · 492 lines · 19 tokens per session scan A 748d2acc9f4b
continuous-cost-monitor is a skill published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 3,686 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-09-03.
Other skills, from other repositories
iac-apply
Actually APPLY an Infrastructure-as-Code change — the highest-stakes mutator in nyann; it can mutate real cloud infrastructure. Re-runs the plan, shows it, confirms with the user, then invokes bin/iac-apply.sh --apply (adding --confirm-destroy only when the user explicitly confirms a destructive change). UNMISTAKABLY…
iac-plan
Preview an Infrastructure-as-Code change WITHOUT applying it. Runs bin/iac-plan.sh, which detects the repo's IaC tool (terraform, opentofu, aws-cdk, pulumi, helm, kubernetes, kustomize, ansible), shells out to the user's already-authenticated CLI, and renders a normalized add/change/destroy summary. READ-ONLY — it…
Capacity, Performance & Cost Assumptions
Ensure architecture/design docs state traffic assumptions, performance budgets, resource limits, and cost risks for critical paths.
External Dependencies & Vendor Risks
Ensure designs document third-party dependencies, SLAs, quotas, failure modes, and vendor lock-in mitigation.
activate-site
Activates and provisions a Power Pages website in a Power Platform environment via the Power Platform REST API. Use when the user wants to activate, provision, turn on, or enable a Power Pages website or portal.
deploy-to-connect
Deploy or publish Python and R content to a Posit Connect server using rsconnect-python or the R rsconnect package. Handles interactive apps and dashboards, web APIs, rendered documents, and prepared bundles/manifests. Use whenever the user asks to deploy, publish, or redeploy content to Posit Connect, or mentions…