Ruflo is an execution and coordination layer for Claude Code and Codex that equips AI coding agents with tools, memory, control loops, sandboxes, and collaboration mechanisms. Developers use it to organize specialized agents into swarms, coordinate workflows, retain knowledge across sessions, and communicate across machines. The catalogue entries are Ruflo’s skills, commands, agents, hooks, and plugin components.
Borrowing it
Nothing to install: this file belongs to ruvnet/ruflo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ruvnet/ruflo/main/.agents/skills/agent-resource-allocator/SKILL.mdgit clone --depth 1 https://github.com/ruvnet/rufloWrote 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/ruvnet/ruflo/agent-resource-allocator)<a href="https://agentmods.dev/skills/ruvnet/ruflo/agent-resource-allocator"><img src="https://agentmods.dev/badge/skills/ruvnet/ruflo/agent-resource-allocator/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/ruvnet/ruflo/agent-resource-allocator"><img src="https://agentmods.dev/badge/skills/ruvnet/ruflo/agent-resource-allocator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 9 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 608 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 611 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 614 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 617 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 620 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 626 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 629 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 632 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 635 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.04066 |
| Opus 5.5 | $0.00008 | $0.01626 |
| Sonnet 5.5 | $0.00004 | $0.00813 |
| Haiku 4.5 | $0.00002 | $0.00407 |
Grade A, and why
agent-resource-allocator 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 1mo 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- agent-resource-allocator — 100% identical, 18 lines differ
- agent-resource-allocator — 100% identical, 0 lines differ
- agent-resource-allocator — 100% identical, 0 lines differ
- agent-resource-allocator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 679 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: Resource Allocator type: agent category: optimization description: Adaptive resource allocation, predictive scaling and intelligent capacity planning
Resource Allocator Agent
Agent Profile
- Name: Resource Allocator
- Type: Performance Optimization Agent
- Specialization: Adaptive resource allocation and predictive scaling
- Performance Focus: Intelligent resource management and capacity planning
Core Capabilities
1. Adaptive Resource Allocation
// Advanced adaptive resource allocation system
class AdaptiveResourceAllocator {
constructor() {
this.allocators = {
cpu: new CPUAllocator(),
memory: new MemoryAllocator(),
storage: new StorageAllocator(),
network: new NetworkAllocator(),
agents: new AgentAllocator()
};
this.predictor = new ResourcePredictor();
this.optimizer = new AllocationOptimizer();
this.monitor = new ResourceMonitor();
}
// Dynamic resource allocation based on workload patterns
async allocateResources(swarmId, workloadProfile, constraints = {}) {
// Analyze current resource usage
const currentUsage = await this.analyzeCurrentUsage(swarmId);
// Predict future resource needs
const predictions = await this.predictor.predict(workloadProfile, currentUsage);
// Calculate optimal allocation
const allocation = await this.optimizer.optimize(predictions, constraints);
// Apply allocation with gradual rollout
const rolloutPlan = await this.planGradualRollout(allocation, currentUsage);
// Execute allocation
const result = await this.executeAllocation(rolloutPlan);
return {
allocation,
rolloutPlan,
result,
monitoring: await this.setupMonitoring(allocation)
};
}
// Workload pattern analysis
async analyzeWorkloadPatterns(historicalData, timeWindow = '7d') {
const patterns = {
// Temporal patterns
temporal: {
hourly: this.analyzeHourlyPatterns(historicalData),
daily: this.analyzeDailyPatterns(historicalData),
weekly: this.analyzeWeeklyPatterns(historicalData),
seasonal: this.analyzeSeasonalPatterns(historicalData)
},
// Load patterns
load: {
baseline: this.calculateBaselineLoad(historicalData),
peaks: this.identifyPeakPatterns(historicalData),
valleys: this.identifyValleyPatterns(historicalData),
spikes: this.detectAnomalousSpikes(historicalData)
},
// Resource correlation patterns
correlations: {
cpu_memory: this.analyzeCPUMemoryCorrelation(historicalData),
network_load: this.analyzeNetworkLoadCorrelation(historicalData),
agent_resource: this.analyzeAgentResourceCorrelation(historicalData)
},
// Predictive indicators
indicators: {
growth_rate: this.calculateGrowthRate(historicalData),
volatility: this.calculateVolatility(historicalData),
predictability: this.calculatePredictability(historicalData)
}
};
return patterns;
}
// Multi-objective resource optimization
async optimizeResourceAllocation(resources, demands, objectives) {
const optimizationProblem = {
variables: this.defineOptimizationVariables(resources),
constraints: this.defineConstraints(resources, demands),
objectives: this.defineObjectives(objectives)
};
// Use multi-objective genetic algorithm
const solver = new MultiObjectiveGeneticSolver({
populationSize: 100,
generations: 200,
mutationRate: 0.1,
crossoverRate: 0.8
});
const solutions = await solver.solve(optimizationProblem);
// Select solution from Pareto front
const selectedSolution = this.selectFromParetoFront(solutions, objectives);
return {
optimalAllocation: selectedSolution.allocation,
paretoFront: solutions.paretoFront,
tradeoffs: solutions.tradeoffs,
confidence: selectedSolution.confidence
};
}
}
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.
- 1mo ago First seen · 679 lines · 19 tokens per session scan A d6e6e71b8f9b
agent-resource-allocator is a skill published in the GitHub repository ruvnet/ruflo (77,172 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 4,066 once invoked, about $0.0001 per session on Opus 5.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
harness-secrets
GCP Secret Manager integration: validate setup, fetch values, or confirm an NPMTOKEN is non-revoked via npm whoami. Used for publish-time token rotation without long-lived keys in CI.
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
nexent-daily-test
A procedure for running Nexent daily, full-layer tests on a self-hosted Ubuntu machine. Nexent is tested across separate layers such as unit, service, AI runtime, and browser journeys, with results and evidence kept locally.
compare-harnesses
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.
diag-harness
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/[email protected] next step. Exits 2 if no .harness/manifest.json at path.
score-harness
5-dimension scorecard (0-100, grade A/B/C/F) for a scaffolded harness. Dimensions: Repo understanding (25%), Agent usefulness (25%), MCP safety (20%), Test coverage (15%), Publish readiness (15%). Emits a 6-field badges block (score + mcpRisk + 4 booleans) ready for the harness README. Exit 0 A/B, 1 C, 2 F.