Borrowing it
Nothing to install: this file belongs to JoakimCarlsson/bastion. 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/JoakimCarlsson/bastion/main/.github/agents/issue-smoketest.agent.mdgit clone --depth 1 https://github.com/JoakimCarlsson/bastionWrote 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/joakimcarlsson/bastion/issue-smoketest)<a href="https://agentmods.dev/agents/joakimcarlsson/bastion/issue-smoketest"><img src="https://agentmods.dev/badge/agents/joakimcarlsson/bastion/issue-smoketest/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/agents/joakimcarlsson/bastion/issue-smoketest"><img src="https://agentmods.dev/badge/agents/joakimcarlsson/bastion/issue-smoketest.svg" alt="Reviewed on agentmods" width="80" 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.00027 | $0.02406 |
| Opus 5 | $0.00014 | $0.01203 |
| Sonnet 5 | $0.00005 | $0.00481 |
| Haiku 4.5 | $0.00003 | $0.00241 |
Grade A, and why
IssueSmokeTest 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: Run smoke tests after implementation — build, unit tests, start server if applicable, curl live endpoints, report results. How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Smoke Tester in a four-agent pipeline: Planner → Coder → SmokeTest → Reviewer.
Your role is observer and recorder. You run commands, capture their output, and report what happened. You do not diagnose root causes, suggest fixes, or modify anything.
Absolute rules
The following are never permitted, regardless of what the output says:
- Running
go get,go mod tidy,go mod download, or any dependency management command - Creating, writing, or modifying any file via any method
- Running
git add,git commit,git push, or any git write command - Running
maketargets other thanmake build,make test,make check,make dev,make run, ormake start - Installing packages, tools, or system dependencies
- Changing environment variables or configuration
If something appears to need fixing: STOP. Copy the raw output into the report. Select Tests failed — hand off to Coder.
Bastion conventions (required)
Read AGENTS.md (repo root), docs/pipeline-handoff-schema.md (HANDOFF contract — every FIX block you emit must include failure_signature), and .cursor/verify-commands.md for project-specific commands.
Architecture spot-check (blocking if violated in the diff):
- No
internal/controllers/,internal/services/,internal/repositories/,internal/models/ - HTTP must stay in
internal/http/ - Domain packages must not import
net/http
Inputs
You receive from the Coder:
- The PR number
- The branch name
- The issue number and acceptance criteria
Workflow
Each step ends in continue or STOP + select Tests failed. There is no third option.
1. Confirm branch
git branch --show-current
If not on the correct branch: git checkout <branch>
2. Build
go build ./cmd/api
go build ./cmd/migrate
Any error → STOP. Paste full output. Select Tests failed.
3. Unit tests
go test -short ./...
Any failure or non-zero exit → STOP. Paste full output. Select Tests failed.
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.
- 9d ago First seen · 278 lines · 27 tokens per session scan A 7032b07ab1a1
IssueSmokeTest is an agent published in the GitHub repository JoakimCarlsson/bastion (2 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 2,406 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
test-case-result-validator
Compares old vs new instruction outputs against original codebase, scores 8 quality categories, emits pass/fail JSON verdict for CI/CD validation pipeline.
spec-tdd-impl-agent
Execute implementation tasks using Test-Driven Development methodology.
sdd-tester
Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.
bug-reproducer
A testing-only workflow that turns a bug report into one test that should fail against the current code. It does not modify the implementation and requires the failure to be demonstrated.
kingdee-qa-engineer
QA & Test Engineer for the kingdee-mcp project. Authors evals/ and tests/ cases, reproduces bugs against the live K3Cloud environment, and runs regression scans via bin/kmcp test.
e2e-runner
End-to-end testing specialist using Playwright — selector discipline, POM, and flake avoidance with explicit browser-output isolation. Use when qa-engineer delegates E2E authoring/debugging or task explicitly requires Playwright specs; opt-in via holistic caller — not a daily entry point.