Block AI agents from reading, snapshotting, and automating your site. Alias for @brainrotcreations/agent-block.
React integration for agent-block
Next.js integration for agent-block — middleware + client script
Compile ES2015 block scoping (const and let) to ES5
Babel plugin to ensure function declarations at the block level are block scoped
[](https://www.npmjs.com/package/@aws-sdk/middleware-user-agent) [](https://www.npmjs.c
Allow parsing of class static blocks
Transform class static blocks
An http(s).Agent implementation that block request Private IP address.
Turn a function into an `http.Agent` instance
[](https://www.npmjs.com/package/@aws-sdk/util-user-agent-browser) [](https://www.n
Parse and lookup IP network blocks
Maps proxy protocols to `http.Agent` implementations
A simple code writer that assists with formatting and visualizing blocks of code.
An HTTP(s) proxy `http.Agent` implementation for HTTPS
[](https://www.npmjs.com/package/@aws-sdk/util-user-agent-node) [](https://www.npmjs.com/
the http/https agent used by the npm cli
Global HTTP/HTTPS proxy configurable using environment variables.
HTTP Agent that keeps socket connections alive between keep-alive requests. Formerly part of mikeal/request, now a standalone module.
A suite of parsers and compilers for WordPress styles.
Get a user agent string across all JavaScript Runtime Environments
An HTTP(s) proxy `http.Agent` implementation for HTTP
A SOCKS proxy `http.Agent` implementation for HTTP and HTTPS
code block extension for tiptap
Lua-first Agent Runtime built on AgentMesh
LLM amplification engine — MCP server with Lua scripting
algocline application layer — execution orchestration, package management
algocline domain model and metrics — pure execution state machine
algocline Lua execution engine — VM, session, bridge
algocline MCP server adapter — thin tool/handler layer over algocline-app
Kernai is an AI agent kernel based on a universal XML block protocol, enabling simple, dynamic, observable and fully controlled orchestration without external runtime dependencies. Ships with reference provider adapters for Anthropic, OpenAI and Ollama, native multimodal support, a workflow DAG scheduler, pluggable recorder sinks and an optional MCP (Model Context Protocol) bridge.
This agent supports Instrumental custom metric monitoring for Ruby applications. It provides high-data reliability at high scale, without ever blocking your process or causing an exception.
Middleware for blocking requests to rake apps based on user agent, remote IP, and other environment variables.
Phronomy provides composable building blocks — Agents, Workflows, Tools, Guardrails, and Tracing — for building AI agents in Ruby. Powered by RubyLLM for LLM abstraction.
A lightweight, non-blocking APM agent that monitors errors and performance metrics with client-side aggregation.
pikuri-skills implements the Agent Skills standard (agentskills.io) for pikuri-core agents: a +Pikuri::Skill::Catalog+ that discovers skill folders under .pikuri/skills, .claude/skills, and .agents/skills; a +Pikuri::Skill::SkillTool+ that loads a skill's body on demand; and a +Pikuri::Skill::Extension+ that wires both into a +Pikuri::Agent+ via +c.add_extension(...)+ in the +Agent.new+ block.
pikuri-tasks gives a pikuri-core agent an in-memory task list it can use to plan and track multi-step work. A +Pikuri::Tasks::List+ holds the per-Agent state; four tools (+task_create+, +task_in_progress+, +task_completed+, +task_delete+) mutate it via content-as-identifier (no item IDs to hallucinate). +Pikuri::Tasks::Extension+ wires the list and tools onto an +Pikuri::Agent+ via +c.add_extension(...)+ inside the +Agent.new+ block. The list lives in process memory only — nothing is written to disk. Sub-agents do not inherit the parent's list (consistent with the "sub-agents do not inherit extensions" rule).
pikuri-subagents owns the sub-agent (delegation) feature top to bottom: the +Pikuri::SubAgent::SubAgentTool+ class (exposed to the LLM as the +agent+ tool), the +Persona+ record, the +Extension+ that wires it onto an agent, and the bundled +Pikuri::SubAgent::RESEARCHER+ persona (network-read only). Hosts that want sub-agents add this gem as a runtime dep and call +c.add_extension Pikuri::SubAgent::Extension.new(personas: [...])+ inside their +Agent.new+ block — same opt-in shape as +pikuri-skills+ / +pikuri-mcp+. Also ships +bin/pikuri-minions+ as a fan-out delegation demo.
A Jekyll generator that writes a .md file alongside each rendered HTML page, so AI agents and crawlers can fetch clean Markdown (with a small machine- friendly frontmatter block) instead of parsing HTML. Configurable per collection.
pikuri-mcp adds Model Context Protocol support to pikuri-core agents: a +Pikuri::Mcp::Registry+ for declaring stdio + HTTP MCP servers, the +Pikuri::Mcp::Servers+ runtime that spawns them, a +Pikuri::Mcp::Synthesizer+ that LLM-fills missing server descriptions, a +Pikuri::Mcp::Verifier+ that screens server surfaces for prompt-injection patterns before any tool is advertised to the LLM, and a +Pikuri::Mcp::Extension+ that wires everything into a +Pikuri::Agent+ via +c.add_extension(...)+ in the +Agent.new+ block.
pikuri-vectordb gives a pikuri-core agent a +vectordb_search+ tool over a local document corpus — agentic search, the agent decides when to retrieve. Ships a swappable backend (a pure-Ruby +Backend::InMemory+ for teaching and a thin +Backend::Chroma+ HTTP client for persistence), a chunker, an embedder wrapper over +RubyLLM.embed+, and an optional +Reranker::LlamaServer+ that speaks +/v1/rerank+ against a cross-encoder model. Text extraction goes through +Pikuri::FileType.read_as_text+ in pikuri-core, which handles plain text / Markdown / PDF; HTML extraction is a deferred follow-up. Hosts wire the feature via +c.add_extension Pikuri::VectorDb::Extension.new(...)+ inside the +Agent.new+ block — same opt-in shape as +pikuri-tasks+ / +pikuri-skills+. The bundled +Pikuri::VectorDb::LIBRARIAN+ persona is the privilege-separated sub-agent counterpart for hosts that want recall to flow through a child rather than the parent's context. Three model endpoints in the full setup — chat (via ruby_llm), an embedder (via +RubyLLM.embed+), and an optional reranker (HTTP +/v1/rerank+). A single +llama-server+ in router mode serves all three by default, loading each cached GGUF on demand; see the gem's README for details.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.