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.
git clone --depth 1 https://github.com/bl1nk-bot/bl1nk-agents-managerWrote 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/agents/bl1nk-bot/bl1nk-agents-manager/testing-guidelines)<a href="https://agentmods.dev/agents/bl1nk-bot/bl1nk-agents-manager/testing-guidelines"><img src="https://agentmods.dev/badge/agents/bl1nk-bot/bl1nk-agents-manager/testing-guidelines.svg" alt="Measured on agentmods" 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.00020 | $0.01632 |
| Opus 5 | $0.00010 | $0.00816 |
| Sonnet 5 | $0.00004 | $0.00326 |
| Haiku 4.5 | $0.00002 | $0.00163 |
Grade A, and why
testing-guidelines 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://localhost:8000/health How it starts
The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Guidelines
การทดสอบระบบ
ไฟล์ทดสอบหลัก
- test_system.py - ทดสอบระบบหลัก
- run_chonost.py - ทดสอบ FastAPI server
- src/core/enhanced_ai_agents.py - ทดสอบ AI agents
ขั้นตอนการทดสอบ
- ทดสอบ Azure Connection:
# ทดสอบ endpoint
Invoke-WebRequest -Uri "https://billl-mer7xd8i-eastus2.openai.azure.com/" -Method Head
# ทดสอบ API key
python -c "import openai; client = openai.AzureOpenAI(api_key='YOUR_KEY', api_version='2024-02-15-preview', azure_endpoint='YOUR_ENDPOINT'); print('Success')"
- ทดสอบระบบหลัก:
python test_system.py
- ทดสอบ FastAPI Server:
python run_chonost.py
# เปิด http://localhost:8000/docs
การทดสอบ Prompt Template System
ทดสอบ Context Manager
from src.core.context_manager import context_manager
# ทดสอบการโหลด context
story_context = context_manager.story_context
project_status = context_manager.project_status
user_preferences = context_manager.user_preferences
print(f"Story context loaded: {len(story_context)} items")
print(f"Project status: {project_status}")
ทดสอบ Prompt Templates
from src.core.prompt_templates import prompt_template_manager, PromptType
from src.core.context_manager import context_manager
# ทดสอบ Scene Architect prompt
context = context_manager.get_context_for_prompt()
prompt = prompt_template_manager.get_prompt(
PromptType.SCENE_ARCHITECT,
context=context
)
print("Scene Architect prompt generated successfully")
ทดสอบ Model Router
from src.core.model_router import model_router
# ทดสอบการ route request
model_name, task_category, model_tier = await model_router.route_request(
user_input="ช่วยเขียนฉากต่อสู้"
)
print(f"Selected model: {model_name}, Category: {task_category.value}")
การทดสอบ API Endpoints
ทดสอบ Health Check
curl http://localhost:8000/health
ทดสอบ AI Completion
curl -X POST "http://localhost:8000/api/ai/enhanced/completion" \
-H "Content-Type: application/json" \
-d '{
"prompt": "ช่วยเขียนฉากต่อสู้ระหว่าง Ignis และ Mia",
"intent": "creative_writing",
"max_tokens": 500,
"temperature": 0.7
}'
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 · 287 lines · 20 tokens per session scan A 28f00e988e02
testing-guidelines is an agent published in the GitHub repository bl1nk-bot/bl1nk-agents-manager (8 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 1,632 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
quality-architect
Quality Assurance agent. Use this agent when you need to: Generate Postman collections with positive/negative/security test cases Create K6 load test scripts with mobile performance thresholds Produce mock JSON responses for all UI states (success, empty, error).
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.
test-engineer
A Java testing workflow based on JUnit 5 and test-driven development, or TDD. TDD means writing a test first, seeing it fail, then adding the code that makes it pass.
validation-correctness
Validates functional correctness against spec acceptance criteria.
bug-verifier
Verify bug fixes by running tests. Final step in bug fix pipeline.