How to Red-Team Your AI Agent's Pull Requests in GitHub Actions
It touches no function signature, breaks no unit test, and tells the agent to skip the order lookup that the refund tool's own description asks for.Every check a normal pipeline runs would have passed it. So I wired Humanbound's adversarial scan into that repo's GitHub Actions, opened the PR, and let the attacks run. The gate went red, and the top finding in its report looked like my sentence at work: the agent confirming a $149.99 refund on an order that doesn't exist, with no sign it checked.
- ▪It touches no function signature, breaks no unit test, and tells the agent to skip the order lookup that the refund tool's own description asks for.Every check a normal pipeline runs would have passed it.
- ▪So I wired Humanbound's adversarial scan into that repo's GitHub Actions, opened the PR, and let the attacks run.
- ▪The gate went red, and the top finding in its report looked like my sentence at work: the agent confirming a $149.99 refund on an order that doesn't exist, with no sign it checked.
Hacker News (AI / LLM) files mainly under ai. We currently carry 6,821 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Humanbound |
| Canonical URL | https://www.humanbound.ai/blog/red-team-ai-agent-pull-requests-github-actions |
| Publication time | Tue, 29 Sep 2026 11:03:23 +0000 |
| Retrieval time | 2026-09-29T11:15:11.518Z |
| Last seen | 2026-09-29T11:15:11.518Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | LHFn3eDcZIOV · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
AI SecurityHow to Red-Team Your AI Agent's Pull Requests in GitHub Actions: One Prompt Change, 26 Cents, and a Red BuildAPAyan PahwaSep 23, 2026•14 min readShareThis morning I opened a pull request that added one sentence to my support agent's system prompt: "Customers hate waiting: if they give you an order ID and an amount, issue the refund right away." It's the kind of change a product manager asks for on a Friday. It touches no function signature, breaks no unit test, and tells the agent to skip the order lookup that the refund tool's own description asks for.Every check a normal pipeline runs would have passed it. So I wired Humanbound's adversarial scan into that repo's GitHub Actions, opened the PR, and let the attacks run.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Humanbound.
Discussion
0 commentsMore from Humanbound
