bubbaloop-core-contributor

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.

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.

Security

Grade A, and why

bubbaloop-core-contributor scanned grade A with 1 finding 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 2d 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.

bubbaloop-mcp/agents/bubbaloop-core-contributor.md · 127 lines

How it starts

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

#[tool(
    name = "noun_verb",
    description = "One sentence. Concrete enough that a small Llama / Qwen model picks it correctly.",
    annotations(
        title = "Noun verb",
        read_only_hint = false,
        destructive_hint = false,
        idempotent_hint = true,
        open_world_hint = false,
    )
)]
async fn noun_verb(
    &self,
    Parameters(req): Parameters<NounVerbRequest>,
) -> Result<CallToolResult, rmcp::ErrorData> {
    log::info!("[MCP] tool=noun_verb arg={}", req.thing);
    if let Err(e) = validation::validate_thing(&req.thing) {
        return Ok(CallToolResult::success(vec![Content::text(format!("Validation: {}", e))]));
    }
    match self.platform.noun_verb(req).await {
        Ok(out) => Ok(CallToolResult::success(vec![Content::text(out)])),
        Err(e) => Ok(CallToolResult::success(vec![Content::text(format!("Error: {}", e))])),
    }
}

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.

Related

Other agents, from other repositories