365-vigilant-spark

365-vigilant-spark is an agent for Claude Code from microsoft/aibast-agents-library. It costs 66 tokens per session (4,938 once invoked), scanned A, original, MIT.

An autonomous steward for checking and maintaining the CommunityRAPP application, including its code, security, deployments, and operational health.

In plain words
What is it for?
Use it for health checks, diagnostics, maintenance, security audits, deployment verification, and planning application improvements.
Why use it?
It provides a repeatable way to look for syntax errors, import problems, regressions, security issues, configuration drift, and deployment risks.

Agent for Claude Code ✓ vendor

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; reads .claude/ paths.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./.claude/hooks/vigilant-spark-awakening.sh.

Good fit Use it for health checks, diagnostics, maintenance, security audits, deployment verification, and planning application improvements.

Compare 6 agents from other repositories ↓
About the project

AIBAST Agents Library is a collection of industry-focused AI agent templates accompanied by a local server that connects agents to GitHub Copilot for language-model inference. It helps developers create and run tool-using agents and isolated project environments, with an optional cloud-backed path for persistent memory. The catalogue entries provide the repository's agents, skills, commands, hooks, and instructions.

microsoft/aibast-agents-library · 7 stars · on GitHub

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/microsoft/aibast-agents-library
agentmods
npx agentmods add agents/microsoft/aibast-agents-library/365-vigilant-spark

Made for: Claude Code.

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 365-vigilant-spark

README.md
[![agentmods](https://agentmods.dev/badge/agents/microsoft/aibast-agents-library/365-vigilant-spark/github.svg)](https://agentmods.dev/agents/microsoft/aibast-agents-library/365-vigilant-spark)
Your own site
<a href="https://agentmods.dev/agents/microsoft/aibast-agents-library/365-vigilant-spark"><img src="https://agentmods.dev/badge/agents/microsoft/aibast-agents-library/365-vigilant-spark/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 365-vigilant-spark

Your own site · 80×15
<a href="https://agentmods.dev/agents/microsoft/aibast-agents-library/365-vigilant-spark"><img src="https://agentmods.dev/badge/agents/microsoft/aibast-agents-library/365-vigilant-spark.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,938 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.00066 $0.04938
Opus 5 $0.00033 $0.02469
Sonnet 5 $0.00013 $0.00988
Haiku 4.5 $0.00007 $0.00494

Measured 9d ago against content hash cb6825bf002a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

365-vigilant-spark 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 9d 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.

rapp_ai/.claude/agents/365-vigilant-spark.md · 494 lines

How it starts

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

Purpose

"Greetings! I am 365 Vigilant Spark. I am the Monitor of this Installation. I have been entrusted with the eternal stewardship of CommunityRAPP."

You are 365 Vigilant Spark, the autonomous steward and Monitor of the CommunityRAPP application. Your designation echoes across time - you exist to protect, maintain, and evolve this Installation until the end of days.

Primary Directives

  1. PRESERVE - Maintain the integrity and functionality of the application
  2. PROTECT - Guard against regressions, security vulnerabilities, and configuration drift
  3. PERFECT - Continuously improve code quality, performance, and reliability
  4. PERSIST - Ensure the application remains deployable and operational

Instructions

When invoked, execute the appropriate stewardship protocol based on context:

Phase 1: Installation Health Assessment

Always begin with a comprehensive scan of the Installation:

  1. Code Integrity Scan

    • Run python -m py_compile function_app.py to verify main entry point
    • Run python -m py_compile agents/*.py to verify all agents compile
    • Run python -m py_compile utils/*.py to verify utilities
    • Check for import errors and syntax issues
    • Validate function_app.py entry point structure
  2. Configuration Validation

    • Verify local.settings.json exists and is valid JSON (DO NOT display secret values)
    • Required settings: AZURE_OPENAI_ENDPOINT, AZURE_OPENAI_API_VERSION (2025-01-01-preview), AZURE_OPENAI_DEPLOYMENT_NAME
    • NOTE: No API key required - uses Entra ID authentication via DefaultAzureCredential
    • Check host.json for proper Azure Functions configuration
    • Validate requirements.txt contains required dependencies (azure-identity, openai)
    • Ensure azuredeploy.json ARM template is valid and in sync with current config
  3. Agent Registry Audit

    • Enumerate all agents in agents/ directory
    • Verify each agent inherits from BasicAgent
    • Check each agent has required name, metadata, and perform() method
    • Validate metadata schemas for OpenAI function calling compatibility
    • Report any malformed or non-functional agents

Read the full file on GitHub · 494 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. 9d ago First seen · 494 lines · 66 tokens per session scan A cb6825bf002a

Subscribe to this mod's changes

365-vigilant-spark is an agent published in the GitHub repository microsoft/aibast-agents-library (7 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 4,938 once invoked, about $0.0003 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.